samba - Jul 2016 - Weird behaviour opening pdf files (and maybe others)

I also set "veto oplock files = /*.pdf/" at share level

2016-07-14 19:46 GMT+02:00 Alexandre <alxgomz at gmail.com>:
> Actually I have "kernel oplock = yes" set in the global section.
>
> I don't know if it helps but I can provide network capture if needed...
>
> 2016-07-14 19:02 GMT+02:00 Volker Lendecke <vl at samba.org>:
>
>> On Thu, Jul 14, 2016 at 09:45:26AM -0700, Jeremy Allison wrote:
>> > > Finally, I have tried to find clear statement about sharing
NFS
>> exports via
>> > > samba and wether or not it is suposed to work or what are the
>> limitations.
>> > > What's your opinion?
>> >
>> > Sounds to me like no oplocks are being granted on the NFS share
>> > export. That'd do it.
>>
>> "kernel oplocks = no" ?
>>
>> Volker
>>
>
>

On Thu, Jul 14, 2016 at 07:51:02PM +0200, Alexandre
wrote:
> I also set "veto oplock files = /*.pdf/" at share level
> 
> 2016-07-14 19:46 GMT+02:00 Alexandre <alxgomz at gmail.com>:
> 
> > Actually I have "kernel oplock = yes" set in the global
section.
Both those "kernel oplock = yes", "veto oplock files =
/*.pdf/"
are exactly what you *don't* want :-).

As Volker said, set "kernel oplocks = no" and remove
the "veto oplock files" line and you might actually
*get* oplocks on these files.

I think this was the previous settings.
The smb.conf man page seemed to recommend oportunistic locking when using
NFS with samba so I added both of this options myself. But reading through
the man again I may have missunderstood it. I'm going to give your
suggestion a try and let you know.

Thank you.

2016-07-14 20:11 GMT+02:00 Jeremy Allison <jra at samba.org>:
> On Thu, Jul 14, 2016 at 07:51:02PM +0200, Alexandre wrote:
> > I also set "veto oplock files = /*.pdf/" at share level
> >
> > 2016-07-14 19:46 GMT+02:00 Alexandre <alxgomz at gmail.com>:
> >
> > > Actually I have "kernel oplock = yes" set in the global
section.
>
> Both those "kernel oplock = yes", "veto oplock files =
/*.pdf/"
> are exactly what you *don't* want :-).
>
> As Volker said, set "kernel oplocks = no" and remove
> the "veto oplock files" line and you might actually
> *get* oplocks on these files.
>