Below are a number of errors that appeared in a log file today.
I am running Samba v2.2.5 on a Red Hat Linux v7.3 system. The client
experiencing/causing the errors below is a WinXP(SP1) machine.
The log entries below pertain to 2 errors, the first in handling file
"6.zip" and the second in attempting to run file
"DiskeeperWks413zssi.exe". I didn't see the first error occur,
but I
witnessed the second. The file was double-clicked in Windows Explorer,
and nothing seemed to happen. After a couple seconds I noticed that
Windows Explorer was frozen and had to be manually killed.
What is causing the errors below and what can I do to fix them?
Thanks.
----------------------------------------------------
[2002/10/15 04:45:43, 0] smbd/oplock.c:oplock_break(796)
oplock_break: receive_smb timed out after 30 seconds.
oplock_break failed for file NMS Photos/What's NMS About/6.zip (dev =
812, inode = 405606, file_id = 4810).
[2002/10/15 04:45:43, 0] smbd/oplock.c:oplock_break(868)
oplock_break: client failure in oplock break in file NMS Photos/What's
NMS About/6.zip
[2002/10/15 04:45:43, 0] smbd/reply.c:reply_lockingX(4489)
reply_lockingX: Error : oplock break from client for fnum = 13686 and no
oplock granted on this file (NMS Photos/What's NMS About/6.zip).
[2002/10/15 13:45:20, 0] smbd/oplock.c:oplock_break(823)
oplock_break: no break received from client within 30 seconds.
oplock_break failed for file Application Setup/DiskeeperWks413zssi.exe
(dev =812, inode = 600356, file_id = 135).
[2002/10/15 13:45:20, 0] smbd/oplock.c:oplock_break(868)
oplock_break: client failure in oplock break in file Application
Setup/DiskeeperWks413zssi.exe
[2002/10/15 13:45:20, 0] smbd/reply.c:reply_lockingX(4489)
reply_lockingX: Error : oplock break from client for fnum = 8969 and no
oplock granted on this file (Application Setup/DiskeeperWks413zssi.exe).
