Thanks for fixing oplock.c for Linux 2.0 in 2_2 CVS
rabollinger at attbi.com
Thu May 30 21:00:02 GMT 2002
Wouldn't it be neat if we could do _better_ than MS at their own game and somehow prevent the
win9x client bug from getting triggered in case of timeout disconnections?
----- Original Message -----
From: "Jeremy Allison" <jra at samba.org>
To: "Richard Bollinger" <rabollinger at attbi.com>
Cc: "Volker Lendecke" <Volker.Lendecke at SerNet.DE>; "Jeremy Allison" <jra at samba.org>;
<abartlet at samba.org>; "Andrew Bartlett" <abartlet at pcug.org.au>; "Samba Technical"
<samba-technical at samba.org>; <tridge at samba.org>
Sent: Thursday, May 30, 2002 8:30 PM
Subject: Re: Thanks for fixing oplock.c for Linux 2.0 in 2_2 CVS
On Thu, May 30, 2002 at 07:36:21PM -0400, Richard Bollinger wrote:
> Please see: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q297684
Ah - this is very interesting, thanks for pointing this out.
Using the registry setting here :
and setting it to 1 (meaning 1 minute) I have perfectly
reproduced this client problem with Win98 client, W2K
I thought they might have some heuristics to avoid running
into this bug themselves when talking to a Win98 client
but no - it's just that their timeout on autodisconnect
is much longer......
This means we're completely the same as a W2K server in
this respect - we probably need to add a big warning message
to the timeout parameter on the man page, but I don't think
any code changes would help.
More information about the samba-technical