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

[Jeremy Allison]

On Fri, May 24, 2002 at 10:00:43AM -0400, Richard Bollinger wrote:
> How embarassing... still apparently broken / inconsistent :-(
> 
> Client is win98 4.10.1998.
> 
> [2002/05/24 08:36:40, 0] smbd/server.c:main(707)
>   smbd version 2.2.5-pre started.
>   Copyright Andrew Tridgell and the Samba Team 1992-2002
>   (rab at LS01) (gcc version 2.7.2.3) #1 Fri May 24 07:21:54 EDT 2002 i586-pc-linux-gnulibc1
> [2002/05/24 08:36:41, 1] lib/debug.c:debug_message(258)
>   INFO: Debug class all level = 1   (pid 14812 from pid 14812)
> [2002/05/24 08:36:42.394090, 1, pid=14812] smbd/files.c:file_init(166)
>   file_init: Information only: requested 10000 open files, 246 are available.
> [2002/05/24 09:02:09.743130, 1, pid=21159] smbd/service.c:make_connection(653)
>   p139 (x.x.x.x) connect to service tmp as user rab (uid=5255, gid=6641) (pid 21159)
> [2002/05/24 09:02:49.071320, 0, pid=21159] smbd/oplock.c:oplock_break(786)
>   oplock_break: receive_smb timed out after 30 seconds.
>   oplock_break failed for file netbench/netbench.exe (dev = 900, inode = 181, file_id = 1).
> [2002/05/24 09:02:49.098472, 0, pid=21159] smbd/oplock.c:oplock_break(858)
>   oplock_break: client failure in oplock break in file netbench/netbench.exe

Well, this is a client failure to respond. The does happen sometimes,
especially with Winx9 clients - their TCP stack is ... well.... not 
wonderful, let's just say :-).

Dropped packets for whatever reason can also cause this. It doesn't
mean the fix is bad, occasionally this will just happen (it does on
NT servers also, they just don't log the message like we do :-).

Jeremy.