Package: smbfs Version: 3.0.24-6etch10 Severity: normal
This is a problem that completely puzzles me. I'm running a samba server on 'etch' and have ACL's enabled on the filesystem shared by samba. I have clients with 'etch', 'sid', WinXP and Mac OS X. /bin/mount.cifs has setuid set so users can mount shares. They normaly do it by specifying -o user=username,noperm as the uid/gid can be different. Now Windows User can perfectly work and change acls. Mac OS X Users can just work on files, but that's all they need ;-) Linux Users which mount files via mount.cifs experience a very strange problem I have been trying to find for the last couple of days. If they use a text editor like vi or nano (kwrite is also affected) which does not seam to open and lock the file exclusively, they can open the file, but as soon as something is changed and the user tries to save the file they get such an error: Error writing /path/to/file/on/smb/server: No such file or directory Saving under a different name and then renaming the file overwriting the original one works perfectly. Also deleting, creating, renaming, piping data to the file works as expected. Any idea what could cause that problem? (A quick search by google leads to the suspicion I'm not the one observing that problem, but I couldn't find and solution). -Benoit- -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.26.1 Locale: LANG=de_CH, LC_CTYPE=de_CH (charmap=ISO-8859-1) Versions of packages smbfs depends on: ii lib 2.3.6.ds1-13etch8 GNU C Library: Shared libraries ii lib 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 common error description library ii lib 1.4.4-7etch6 MIT Kerberos runtime libraries ii lib 2.1.30-13.3 OpenLDAP libraries ii net 4.29 Basic TCP/IP networking system ii sam 3.0.24-6etch10 Samba common files used by both th smbfs recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
