Jeremy, please: your opinion about oplock_break :-)

[Giulio Orsero]

Many 2.0.x users have the:

[1999/06/23 10:47:48, 0] smbd/oplock.c:oplock_break(773)
  oplock_break resend
[1999/06/23 10:47:58, 0] smbd/oplock.c:oplock_break(773)
  oplock_break resend
[1999/06/23 10:48:08, 0] smbd/oplock.c:oplock_break(773)
  oplock_break resend
[1999/06/23 10:48:18, 0] smbd/oplock.c:oplock_break(790)
  oplock_break: receive_smb timed out after 30 seconds.

problem.

I get this errors with win95/win98 and samba2.0.4b/c on rh60 or 2.0.33/libc5.

I know the samba team is busy, but can you just tell us what you think?
It's something the samba team will eventually fix, or do you consider it not
to be a problem on samba side (as it's said in smb.conf man page) so that we
have to try to change win9x settings in some way to solve this?

I have to do a new samba install for a new customer, and I don't know wheter
to go for 1.9.18 or 2.0.4b just because of this issue.

Thanks.

-- 
giulioo at tiscalinet.it