On Thu, Oct 20, 2011 at 04:30:10PM +0200, lynn wrote:
On Thursday 20 Oct 2011 14:22:46 Lars Müller wrote:
On Thu, Oct 20, 2011 at 02:12:48PM +0200, lynn wrote: [ 8< ]
It works as expected if the file is on an NFS share. If the file is open, subsequent clicks give a read only copy and you can see the dot file created as a lock.
The NFS export you have mounted. Right?
Can you please answer the question? Else I'll stop asking further.
Why don't you mount the Samba share via cifs? Then the same locking mechanism as with NFS would happen.
Thanks. I've tried that but unfortunately the lock file is still not created. The share in smb.conf is: [stuff] comment = Shared stuff path = /home/stuff force group = users create mask = 0660 force create mode = 0660 security mask = 0770 directory mask = 0770 force directory mode = 0770 directory security mask = 0770 read only = No
Doesn't Samba use cifs when accessing the share anyway?
No. Samba uses the _local_ filesystem to export it to cifs client systems (like Microsoft Windows, the Linux kernel cifs client, smbclient, the smb kio slave as part of KDE apps via libsmbclient). There is no need to run Samba's smbd, inparticular to configure a share to access a remote share. Please try to keep it simple and stupid (KISS) and quote only needed parts of a mail and nothing further. Thanks. PS while reading all the mask and mode setting from the share I spontaneously got zits. Using "inherit acls = Yes" per share and a default ACL on filesystem level makes thing much easier. That's also the reason why it is this the default for shares in the smb.conf as part of the Samba package. This results in a Linux filesystem environmant which behaves the same way as it does to cifs clients. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany