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

Green, Paul Paul.Green at
Sat Jun 1 03:58:01 GMT 2002

jra at [mailto:jra at] writes:
> On Fri, May 31, 2002 at 05:50:58PM -0700, Matt Seitz wrote:
> > From: jra at [mailto:jra at]
> > >The only thing would be to completely disallow
> > >connection timeouts for Win9x clients - I'm not sure
> > >this is what we want.....
> > 
> > Perhaps timeouts could be prevented for a 9x client when an 
> > oplock is present?  Or have two timeouts:  a shorter (soft)
> > timeout when an oplock is not present and a longer (hard)
> > timeout even when an oplock is present?
> No, you can't time out at all. Remeber, as soon as you
> time out and drop the connection (TCP RST or FIN) you're
> dead - the client will exhibit this bug.
> There is no way around this with different timeouts, it's
> very simple - drop a connection to a Win9x client, suffer
> an oplock break bug in the client. No other way around this
> client bug.

Is there a way to identify a Win9x client in the datastream?  If so, then
Samba could leave the connection up for these clients....


More information about the samba-technical mailing list