Thanks for your reply.
I noticed that depending on the client I use Samba creates a different
> of lock with different behaviour when multiple clients attempt to open
> same file. Neither smbfs nor cifs create the correct lock share mode
> (DENY_WRITE) and the access mode is different (smbfs:0x3, cifs:0x12019f
> opposed to Windows: 0x2019f)
You're confusing deny modes with locks. They are not the same thing.
Are you talking about locks or deny modes here ?
Yes sorry, I guess I am a bit confused about the difference between the two.
According to my Samba book - "Share (deny) modes are used by clients to gain
exclusive read or write access to a file", which sounds very similar to the
idea of a lock and seems the right mechanism to achieve my desired result.
What I don't understand is why the SMBFS and CIFS kernel modules create a
deny mode DENY_NONE instead of DENY_WRITE when the client opens the file for
read/write access. Shouldn't it always be DENY_WRITE if the client issues a
Is it the deny mode or the hexadecimal access mode (as shown by smbstatus)
that Samba uses to report back to the client that the file is currently
locked for writing?
To unsubscribe from this list go to the following URL and read the