I noticed a difference in byte range locking behavior between Samba (2.2.x) and Windows 2000 server, basically on Samba 2.2.x with strict locking enabled, a client process which owns a shared byte range lock can write to the locked region, this is not allowed on Windows 2000 server. Is there a reason for this Samba behavior? Is it because of default value of some config option?
Sri
