samba - Jul 2002 - Documentation / boolean fix for oplocks = command

In the documentation the "oplocks = yes" option is give in an example,
as
the default for this parameter. However, I needed to turn oplocks off, and
so assumed that the command "oplocks = no" would work. It doesn't,
instead I
found that "oplocks = false" does. There needs to be some boolean
fixing
done, or at least documentation should reflect this strangeness.

Thanks!

Greg Webster
Systems Administration
and Support Technician    
Alexander Holburn Beaudin & Lang

On Thu, 25 Jul 2002, WEBSTER, Greg wrote:
> 
> In the documentation the "oplocks = yes" option is give in an
example, as
> the default for this parameter. However, I needed to turn oplocks off, and
> so assumed that the command "oplocks = no" would work. It
doesn't, instead I
> found that "oplocks = false" does. There needs to be some boolean
fixing
> done, or at least documentation should reflect this strangeness.
That would be really strange then because it would mean that all 
boolean parameters act in this way.  Are you sure?  Not that i doubt 
you...  just have a healthy dose of skepticism.















cheers, jerry
 ---------------------------------------------------------------------
 Hewlett-Packard                                     http://www.hp.com
 SAMBA Team                                       http://www.samba.org
 --                                            http://www.plainjoe.org
 "Sam's Teach Yourself Samba in 24 Hours" 2ed.      ISBN
0-672-32269-2
 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--

Absolutely sure. It didn't work at all with 'oplocks = no' (yep, we
restarted Samba). As soon as we changed it to 'oplocks = False' (and
restarted Samba) it worked flawlessly.

Stats: Samba v2.2.5, Redhat 7.2

Thanks!

Greg
> -----Original Message-----
> From: Gerald Carter [mailto:jerry@samba.org]
> Sent: July 26, 2002 8:57 AM
> To: WEBSTER, Greg
> Cc: 'samba@samba.org'
> Subject: Re: [Samba] Documentation / boolean fix for oplocks = command
> 
> 
> On Thu, 25 Jul 2002, WEBSTER, Greg wrote:
> 
> > 
> > In the documentation the "oplocks = yes" option is give in 
> an example, as
> > the default for this parameter. However, I needed to turn 
> oplocks off, and
> > so assumed that the command "oplocks = no" would work. It 
> doesn't, instead I
> > found that "oplocks = false" does. There needs to be some 
> boolean fixing
> > done, or at least documentation should reflect this strangeness.
> 
> That would be really strange then because it would mean that all 
> boolean parameters act in this way.  Are you sure?  Not that i doubt 
> you...  just have a healthy dose of skepticism.
> 
> 
> 
> 
> 
> cheers, jerry
>  ---------------------------------------------------------------------
>  Hewlett-Packard                                     http://www.hp.com
>  SAMBA Team                                       http://www.samba.org
>  --                                            http://www.plainjoe.org
>  "Sam's Teach Yourself Samba in 24 Hours" 2ed.      ISBN
0-672-32269-2
>  --"I never saved anything for the swim back." Ethan Hawk in
Gattaca--
>

Basically, when we moved the files for our rather ancient accounting
software (Dexco) over to Samba (from Novell filesharing), it slowed to a
crawl. Speaking to the Dexco people, they suggested it was the oplocks
causing a problem. Once I specified 'oplocks = False' it sped up to
(perhaps) a little faster than access to the Novell fileserver was.

No errors or anything...it just didn't work until I did that.

> -----Original Message-----
> From: Gerald Carter [mailto:jerry@samba.org]
> Sent: July 26, 2002 9:37 AM
> To: WEBSTER, Greg
> Cc: 'samba@samba.org'
> Subject: RE: [Samba] Documentation / boolean fix for oplocks = command
> 
> 
> On Fri, 26 Jul 2002, WEBSTER, Greg wrote:
> 
> > 
> > Absolutely sure. It didn't work at all with 'oplocks = no'
(yep, we
> > restarted Samba). As soon as we changed it to 'oplocks =
False' (and
> > restarted Samba) it worked flawlessly.
> > 
> > Stats: Samba v2.2.5, Redhat 7.2
> 
> What do the logs say though.  I mean is there an error 
> about an unknown parameter value?  or do you actually see smbd 
> giving out oplocks?
> 
> 
> 
> 
> 
> 
> 
> 
> cheers, jerry
>  ---------------------------------------------------------------------
>  Hewlett-Packard                                     http://www.hp.com
>  SAMBA Team                                       http://www.samba.org
>  --                                            http://www.plainjoe.org
>  "Sam's Teach Yourself Samba in 24 Hours" 2ed.      ISBN
0-672-32269-2
>  --"I never saved anything for the swim back." Ethan Hawk in
Gattaca--
>