similar to: Illegal characters in filename?

Hi all, We are sharing directories from Windows 2003 server to, among other things, Mac computers. Most of the time the windows shares work perfectly. However we are running into a problem with users entering odd characters into file names on the Mac clients. The Mac clients see these files/folders perfectly fine, as samba on the Mac allows for these odd characters. However, if someone tries

Does anyone have a solution for the problem of file and directory names containing characters which are OK in DOS/Windows but illegal (or at least unwise) in Unix? I have Windows clients who have written directory names containing "$" characters to Samba shares on a Solaris box. This is fine for the clients, but plays havoc with Solaris programs needing to access the files, eg. backups

This patch adds a switch --fat-filenames which replaces all characters that aren't legal on FAT filesystems with an underscore. This is the first time I touch the rsync code, so I may not be going about it the right way, but it seems to be working. Naturally there's some potential for collisions, but it's probably better than what happens currently (such files are simply not copied).

Hi, I meet a strange trouble writing shapefiles with write.pointShape() from maptools. > write.pointShape(mylines[,5:9], file="Sxtplinshp", mycoordspt) Error in write.pointShape(mylines[, 5:9], file = "Sxtplinshp", mycoordspt) : shapefile names must conform to the 8.3 format It seems that the function request a special shapefile name spelling (conformed to 8.3

Greetings. I have a Windows share mounted via Samba. I recently tried to rename some files; the destination filenames had some high-bit characters. The renaming had some completely unexpected consequences; the new filenames now contain the full pathname (including backslashes), plus other illegal characters (colons). The files can no longer be accessed or modified, either from the remote

I'm running Samba 3.32 on my linux server to share files with the windows computers on the network. My problem is that windows doesn't support some special characters in filenames, like ' : ', that linux has no problem with. So something (not sure if it's Samba or windows) is mangling directory/file names containing that character into 8.3 names, which makes it very difficult

Hello, Let me explain a scenario There are different Asterisk Servers at different Remote locations. Recording in different formats for FIVE seconds reveals that Format : Size wav : 84 KB gsm : 8.3 KB sln : 84 KB It can be recorded in any format. This is size for five seconds only. We need to transfer these files from different remote servers to a centralized server. We need to play these

Hi, I suppose this question must have been posted a hundred times, but Google brings up nothing useful: Consider "The Wall" from Pink Floyd in an MP3 collection. There's "In The Flesh.mp3" and "In The Flesh?.mp3" as tracks. Or, another example in an MP3 collection: There's a Band called "Stellar", but there's also a band called

Hello, I need to use the ${DATETIME} macro inside the filename saved by Record, but the colons (':') used in the time interfere with the command (everything after the colon is interpreted as the format I wish to save to): My command is: Record(/path/to/voicemail/${EXTEN}-${DATETIME}-${UNIQUEID}:wav) I need some function to escape the colons inside DATETIME... I'm sure it's

Maybe controversial, but we really must do something about sanitizing names. An alternative would be to escape the name before including it in the RHEV XML. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org -------------- next part

Hi all I've set up Dovecot to use maildir-storage according to the previous hint from Blair Zajac, and it's working perfectly. However, I still have a problem with the way procmail wants to name the received emails. The following is a slightly modified extract from my logs: procmail: [5373] Thu Feb 5 23:59:14 2004 procmail: Assigning "MAILDIR=/Users/name/Maildir/"

Hello, Last evening I did this recursive rsync: rsync -avz data /mnt/RICEX0/DWT/Daredevil/1071865403/ ..where data is a regular ext3 soft-RAID1 volume ...where /mnt/RICEX0/ is an NTFS hard-RAID10 volume mounted across VPN using SMB. And received errors that look to be generated by smb while trying to recreate(?) the illegal characters. Dec 20 04:30:55 daredevil kernel: smb_create:

Hi, I came across the problem with rsync-2.5.5 on Cygwin/Win2K while rsyncing with filenames which have 'strange' (non latin-1) characters in filenames. The problem is that filenames on Windows system are coded (in our case) in codepage 852, while server (Linux system) has filename coding according to ISO-8859-2. This two are not fully compatible, causing rsync to simply skip copying some

SAMBA Gurus (Both on the mailing list and in the nesgroup): I am running 1.9.18p8 on our production server and 2.0beta4 on a test server. Both are HP-UX 10.20. Hundreds of happy end-users quietly sharing files. Except one. He runs the Adobe Acrobat Catalog program on his Windows NT 4.0 machine. It fails, whether connected to the production server or test server. Granted, this is an old

There are a couple of bug reports on the Debian rsync package about problems with a recipient filesystem that can't cope with all possible unix filenames. Notably filenames with question marks are a problem... I guess that people are trying to backup systems to a SMB share which presumably is then regularly backupped to tape. This basically sounds like a reasonable thing to do :-) Would

Hello all I'm having a problem that is driving me nuts. I am syncing directories that have characters which are not 7-bit Latin encoded, ie. ??? ' and the likes. I'm using a windows/cygwin client machine on one side and a FreeBSD server on the other side. I use an include/exclude list to specify which directories to sync. If I have a c:\backup\l?l c:\backup\bla I put +

Hello all, after endless searching for days you might be able to help. In short: Is there a way to get Samba accept only 8.3 filenames and directory names on a share? The problem: From a windows client a user should be able to save files on a destination (samba share) which aren't longer than the old 8.3 dos convention. This is a requirement for a system behind it, which can only deal

Thanks Tomas, I confirm the R Under development (unstable) (2018-04-26 r74651) version works for Rscript when the file name has a space, and no arguments are specified. C:\>"C:\Program Files\R\R-devel\bin\x64\Rscript.exe" "C:\foo bar.R" R Under development (unstable) (2018-04-26 r74651) Platform: x86_64-w64-mingw32/x64 (64-bit) Running under: Windows 7 x64 (build 7601)

Hello List, Can anyone please help explain how Samba handles long filename conversion to DOS 8.3 tilde format? I have a client with a Windows app that works great when using 8.3 type filenames. When an attempt to use long filenames is made, the files are created great and the data is there. But when the app builds the index and attempt to retrieve the data file is made, the wrong file is

I am backing up files from Linux to a NTFS using rsync. I have the NTFS mounted on Linux via CIFS. I am discovering errors while attempting to backup files with restricted NTFS characters, like : [colon]. For example, I am unable to backup my crucial maildirs, as a colon is encoded in each Linux file path. Is there a solution to rsync Linux file paths with restricted NTFS characters, to NTFS?