Thanks for fixing oplock.c for Linux 2.0 in 2_2 CVS

Jeremy Allison jra at
Wed May 29 13:44:01 GMT 2002

On Sat, May 25, 2002 at 02:05:19PM -0700, Jeremy Allison wrote:
> Well, I've managed to get this to happen to a W2K server too,
> took me a while though.....
> It's definately a client bug with the Win9x client, but we seem
> to trigger it all the time whereas Win2k seems to trigger it sometimes.
> I've also finally got a trace where a W2K server resends an oplock
> break twice, after 300ms - this must be their magic timeout to wake
> up the client.
> This is *extremely* interesting. I'm cc:ing this to tridge directly,
> in case he doesn't believe me :-) :-).

Actually this was a TCP retransmit (shame :-).

Ok - I've played with this a lot and it seems to be completely
reproducible against a W2K SP2 server as well.

If you stop and then restart the "Server" service on W2k, with
a Win98 client connected, then the Win98 client stops responding
to oplock break requests.

Now this is unfortunate in that it happens more to Samba than
to W2K as the idling of connections can cause the serving smbd
to kill itself.

It causes a 30 second wait the first time you try and run an
executable, but after that we stop granting oplocks to that
client and so everything should keep going.


More information about the samba-technical mailing list