Hello Alexey,
Can you tell me about your problem in more details. At first I'd like to
get answer on the following question:
1) Do you use a Debian testing?
2) What samba version do you use?
3) Do you work from regular user account or from root user?
4) How familiar are you with strace and valgrind utilities?
5) Do you know what "locale" is? Do you know how to change it?
(this help to avoid the russian error message)
Then, I need to know your samba, libsmbclient and smbnetfs configuration
1) samba configuration (contents of the file /etc/samba/smb.conf). It's
better to provide the output of "testparm" utility, because smb.conf
contain to much trash
2) libsmbclient configuration (contents of the file ~/.smb/smb.conf from the
user what run smbnetfs)
3) smbnetfs configuration (contents of the file ~/.smb/smbnetfs.conf from the
user what run smbnetfs)
Can you run smbnetfs in debug mode and repeat your test?
There are 2 possibility
1) turn on smbnetfs log (set smbnetfs_debug level). Put the
following line to your ~/.smb/smbnetfs.conf
smbnetfs_debug 6
Possible values are from 0 to 10, but the value of 6 is
usually enough.
2) Turn on samba log (set smb_debug level). Put the following line
to your ~/.smb/smbnetfs.conf
smb_debug number
where the number is a value from 0 to 10 (no any recommendation,
in hard situation i usually use 10)
Sometime the reason of such behavior is the broken tdb database of your
samba server. In this case it helps to delete all "*.tdb" files from
"/var/cache/samba" and it's subdirectories, then restart samba and
winbind (this is safe operation, this files will be recreated)
Mikhail Kshevetskiy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
