Hello all, Either the docs or the value in smb.conf.default is wrong. (Or at least confusing).
On Sat, 15 Sep 2001, ian j hart wrote:> => This parameter defaults to on on systems that have the > support, and off on systems that don't. You should never > need to touch this parameter. > > See also the oplocks and level2 oplocks parameters. > > =>? Default: kernel oplocks = yes > </quote> > > Defaults to yes, but we (FreeBSD) don't have this feature (yet).Doesn't matter. If the kernel doesn't support the feature, the resulting code in Samba (to support kernel oplocks) becomes a no op. I will up date the man page next week. cheers, jerry --------------------------------------------------------------------- www.samba.org SAMBA Team jerry_at_samba.org www.plainjoe.org jerry_at_plainjoe.org --"I never saved anything for the swim back." Ethan Hawk in Gattaca--
Hi, Guys, I think there still are some problems with OPLOCK. I installed Samba2.2.1a on my SuseLinux7.1, my kernel is using 2.4.5 now. I tried to disable/enable 'kernel oplocks' here.Two results I got: 1.Enable 'kernel oplocks' In log message, I got 'set_file_lock: got kernel oplock on file ...' and 'set_file_oplock: granted oplock on file ...', If I only edited that file and saved it on Samba client, I got 'oplock_break: returning success for dev = ...' more 2.Disable 'kernel oplocks' In log message, I got 'set_file_oplock: granted oplock on file ...' only... If I edit that file and saved it on Samba client, I couldn't get same message as section 1. What I cannot understand is in section 1, why I got 'oplock_break: returning success ...' even I haven't opened that same file under Linux box, or NFS client side .. Juer>-----Original Message----- >From: Gerald Carter [mailto:gcarter@valinux.com] >Sent: 17 September 2001 01:54 >To: ian j hart >Cc: samba@lists.samba.org >Subject: Re: kernel oplocks 2.2.1a > > >On Mon, 17 Sep 2001, ian j hart wrote: > >> > I will up date the man page next week. >> >> I know, I looked at the code. But, having correct documentation does >> matter. > >I was pointing out that having 'kernel oplocks = yes' >causes no harm if your kernel doesn't support it. > >> The point is that the two statements above are contradictory, and if >> the first is true then the default value for FreeBSD is wrong. I was >> trying to narrow down a problem with locking. There are 7 options >> (since level2 oplocks requires oplocks). That's a lot of >permutations. >> Removing an option which does nothing saves time and effort. >> >> Since the documentation comes in many formats, you may find it >> easier to just change the default value for FreeBSD in >smb.conf.default. > >It's all in sgml/DocBook source. I already agreed with you and >said I would update the docs next week. Sorry if I wasn't clear. > > > > > > > > >cheers, jerry > --------------------------------------------------------------------- > www.samba.org SAMBA Team jerry_at_samba.org > www.plainjoe.org jerry_at_plainjoe.org > --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba >
Thanks. But , there was only one client accessing that file when I was doing that test. :( And, I sent a email again about that. The question is: If I enable oplock and disable kernel oplock, what will happen? How to produce the conflict?>-----Original Message----- >From: Gerald Carter [mailto:gcarter@valinux.com] >Sent: 17 September 2001 13:21 >To: Juer Lee >Cc: ian j hart; samba@lists.samba.org >Subject: RE: kernel oplocks 2.2.1a > > >On Mon, 17 Sep 2001, Juer Lee wrote: > >> I think there still are some problems with OPLOCK. I installed >> Samba2.2.1a on my SuseLinux7.1, my kernel is using 2.4.5 now. I tried >> to disable/enable 'kernel oplocks' here.Two results I got: >> >> 1.Enable 'kernel oplocks' In log message, I got 'set_file_lock: got >> kernel oplock on file ...' and 'set_file_oplock: granted oplock on >> file ...', If I only edited that file and saved it on Samba client, I >> got 'oplock_break: returning success for dev = ...' more >> >> 2.Disable 'kernel oplocks' In log message, I got 'set_file_oplock: >> granted oplock on file ...' only... If I edit that file and saved it >> on Samba client, I couldn't get same message as section 1. >> >> What I cannot understand is in section 1, why I got 'oplock_break: >> returning success ...' even I haven't opened that same file under >> Linux box, or NFS client side .. > >I don't think this is a problem. The server got an another >exclusive oplock request from a client. You should see this >in the logs. I can't comment more without the full logs. > > > > > > > > >cheers, jerry > --------------------------------------------------------------------- > www.samba.org SAMBA Team jerry_at_samba.org > www.plainjoe.org jerry_at_plainjoe.org > --"I never saved anything for the swim back." Ethan Hawk in Gattaca-- > > >-- >To unsubscribe from this list go to the following URL and read the >instructions: http://lists.samba.org/mailman/listinfo/samba >