[Samba] oplocks

[John Knox]

I am getting this in the error log:

[2002/09/20 14:53:55, 0] smbd/reply.c:reply_lockingX(4413)
  reply_lockingX: Error : oplock break from client for fnum = 7600 and no
oplock granted on (wwwwwwww.doc).
[2002/09/23 09:32:11, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
  call_nt_transact_ioctl: Currently not implemented.
[2002/09/23 10:02:35, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
  call_nt_transact_ioctl: Currently not implemented.
[2002/09/23 16:31:38, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
  call_nt_transact_ioctl: Currently not implemented.
[2002/09/24 08:39:51, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
  call_nt_transact_ioctl: Currently not implemented.
[2002/09/25 08:54:01, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
  call_nt_transact_ioctl: Currently not implemented.
[2002/09/26 08:50:10, 0] smbd/nttrans.c:call_nt_transact_ioctl(1762)
  call_nt_transact_ioctl: Currently not implemented.
[2002/09/26 08:52:08, 0] smbd/oplock.c:oplock_break(813)
  oplock_break: no break received from client within 30 seconds.
  oplock_break failed for file xxxxxx.doc (dev = 12b, inode = 4832).
[2002/09/26 08:52:08, 0] smbd/oplock.c:oplock_break(859)
  oplock_break: client failure in oplock break in file yyyyyyyyyyy.doc
[2002/09/26 08:52:08, 0] smbd/reply.c:reply_lockingX(4413)
  reply_lockingX: Error : oplock break from client for fnum = 8253 and no
oplock granted on this file (zzzzzzzzzzzzzz.doc).

I have noticed suggestions of making:

oplocks = no
level2 oplocks = no
kernel oplocks = no

What exactly does this do?
We are running Win2k clients on a SCO OpenServer 5.0.4 running as a file
server.

The log.nmbd contains the following:

[2002/09/26 11:15:14, 0] nmbd/nmbd_namequery.c:query_name_response(105)
  query_name_response: Multiple (2) responses received for a query on subnet
192.168.xxx.3 for name LANGROUP<1d>.
  This response was from IP 192.168.xxx.2, reportingan IP address of
192.168.xxx.2.
[2002/09/26 11:25:33, 0] nmbd/nmbd_namequery.c:query_name_response(105)
  query_name_response: Multiple (2) responses received for a query on subnet
192.168.xxx.3 for name LANGROUP<1d>.
  This response was from IP 192.168.xxx.2, reportingan IP address of
192.168.xxx.2.
[2002/09/26 11:30:32, 0] nmbd/nmbd_namequery.c:query_name_response(105)
  query_name_response: Multiple (2) responses received for a query on subnet
192.168.xxx.3 for name LANGROUP<1d>.
  This response was from IP 192.168.xxx.2, reportingan IP address of
192.168.xxx.2.
[2002/09/26 11:35:47, 0] nmbd/nmbd_namequery.c:query_name_response(105)
  query_name_response: Multiple (2) responses received for a query on subnet
192.168.xxx.3 for name LANGROUP<1d>.
  This response was from IP 192.168.xxx.2, reportingan IP address of
192.168.xxx.2.

I'm not sure a)	What this means? ... and b)	How to correct it if it is a
problem?

Yours sincerely,

John Knox

SYSTEMS ADMINISTRATOR
RIDER HUNT MELBOURNE 
Phone:	+61 3 9690 6111
Fax:	+61 3 9690 6577
E-mail:	jknox at riderhunt.com.au <mailto:jknox at riderhunt.com.au> 

This e-mail is intended only for the use of the individual or entity named
above and may contain information that is confidential and privileged. If
you are not the intended recipient of this e-mail communication, please
notify us immediately by e-mail to rhm at riderhunt.com.au
<mailto:rhm at riderhunt.com.au>  or reply by e-mail direct to the sender and
then destroy any electronic or paper copy of this message.  Rider Hunt
Melbourne does not represent, warrant or guarantee that the integrity of
this communication has been maintained nor that the communication is free of
errors, virus or interference.