John Drescher <drescherjm <at> gmail.com> writes: > > On Thu, Aug 7, 2008 at 9:16 PM, Doug Germann <76066.515 <at> compuserve.com> wrote: > > Hi-- > > > > We are in a production environment with one WinXP box and several linux boxes. > > > > We have discovered that the WinXP and linux boxes seem to respect each other's > > file locks, but that the linux boxes do not respect each other's locks. In other > > words, box 1 can have a file open, and at the same time box 2 can open it and > > edit and save the file. > > > > We have smb.conf set with level2 oplocks yes, kernel oplocks no, and oplocks no. > > When we first noticed the problem the last two were set to yes. The change has > > made the locks work sometimes, but not reliably. > > > > Are there other things besides the oplocks and the smb.conf file which can > > affect file locking? How would you trouble shoot this? > > > > Are the linux machines sharing the file using samba and mounting the
> share using cifs? > > John Yes. From fstab: //samba1/doug2 /sam/doug2 cifs rw,user,credentials=/[blanked], uid=doug,gid=doug 0 0 :- Doug. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
