[Samba] Illegal characters in filename?

[Andrew Masterson]

The easiest way might be to write a cron script that does a simple tr on
invalid characters to rename files.

Barring that check the "mangled names" parameter for an understanding of
how samba creates the mangled names.

Also of interest might be "mangle prefix", "mangling char", "mangling
method"

-=Andrew

-----Original Message-----
From: samba-bounces at lists.samba.org
[mailto:samba-bounces at lists.samba.org] On Behalf Of Daniel Frey
Sent: Saturday, March 06, 2010 7:55 PM
To: samba at lists.samba.org
Subject: [Samba] Illegal characters in filename?

I have a server that uses both NFS and Samba. I noticed on a Windows
client that some directories and files were in the 8.3 format, and
clicking on them resulted in an "Access denied." message.

I've since upgraded to 3.5.0 - now the "Access denied." message is
gone and I can enter and open files, but all of the names are shown in
the 8.3 format and are almost unreadable. I discovered that the
filenames in question have full colons (:) in them, and this is
illegal for Windows clients. Windows itself won't let you create a
file with an invalid filename.

I have listings like:

T7UFO1~9
--TAHX6K~4.txt
--TAHX6K~B.ods
etc.

I was browsing around in smb.conf's man page looking for a way for
these files to at least be readable. Is there a way to map all of the
invalid characters in Windows that linux can use so they simply appear
as a hyphen (or another character?)

It would be so much easier than having to open each file to identify
them.
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba