[Samba] samba 3.6.9-164 - is "kernel oplocks = no" option viable on purely Samba shared FS?
Karel Lang AFD
lang at afd.cz
Fri Sep 26 00:32:02 MDT 2014
this is great news for me, i can test some more LAN SAmba setting
effects on our PDC :]
Nvm Jeremy, thanks anyway, you replied to your best knowledge, i
appreciate every bit of info :].
Volker, if i might ask, what would be correct setting per share then? I
can't find this documented in man pages or elsewhere ..
is it like?:
kernel oplocks = no
and that is it? or is there some other prerequisites..?
Thanks a lot
On 09/26/2014 12:05 AM, Jeremy Allison wrote:
> On Thu, Sep 25, 2014 at 09:56:06PM +0200, Volker Lendecke wrote:
>> On Mon, Sep 22, 2014 at 09:40:06AM -0700, Jeremy Allison wrote:
>>> On Sun, Sep 21, 2014 at 07:33:19AM +0200, Karel Lang AFD wrote:
>>>> 2 questions:
>>>> In scenario, where you have purely data storage filesystem (no apps,
>>>> databases anything), shared only over Samba and accessed only by
>>>> windows client workstations - would it be OK to use the "kernel
>>>> oplocks = no" option?
>>>> is the "kernel oplocks = no" still Global option??
>> Is that really true?
>> Master has
>> use_kernel = lp_kernel_oplocks(SNUM(fsp->conn))
>> which means we have per-share kernel oplocks.
> Oh ! Serves me right for not checking the
> code before speaking. It *used* to be global :-).
> Sorry Karel, I gave you bad advice there !
> Thanks for checking Volker !
More information about the samba