Backup Central

Craig,

It would appear that some of the file names contain upper ASCII (Binary
values?) that Samba interprets as normal ASCII values. I'm not really
sure whats causing this.

Looking from the Linux side, I have several files that would have a
capital A with an arch over the top of it and others with a lower case a
with the arch.

Looking from the Windows side of things, it does appear that the ones
with the upper case A are bullets (Need to talk to the ISO group to see
what they are doing), but the ones with the lower case a, are not
visible from the Windows 2000 clients.

So, Samba is converting the weird characters to normal ASCII values.
The Arched a is converted to an Upper case A and the same with the
arched lower case a.

Hence, the file not found error.

Still trying to work out whats going on, if it's a client end issue or a
Samba issue.

Anybody have suggestion?

Doug



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Doug Lytle writes:

So, Samba is converting the weird characters to normal ASCII values.
The Arched a is converted to an Upper case A and the same with the
arched lower case a.

Hence, the file not found error.

Still trying to work out whats going on, if it's a client end issue or a
Samba issue.

Anybody have suggestion?

This is from the docs, based on input from GFK.

Also, to make sure that file names with 8-bit characters are
correctly transferred by smbclient you should add this to
samba's smb.conf file for samba 2.x:

[global]
# Accept the windows charset
client code page = 850
character set = ISO8859-1

For samba 3.x this should instead be:

[global]
unix charset = ISO8859-1

This setting should work for western europe. See
L<http://www.oreilly.com/catalog/samba/chapter/book/ch08_03.html>
for more information about settings for other languages.

I don't know anything about charsets and i18n setup for smb.
Hence the reported problems people have with either backing
up or CGI rendering of international charsets.

This would be a great area for someone who knows what they are
doing to submit improvements.

Craig


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/