samba - Jun 1998 - Further to: Samba screwed up when trying to save a word97 document

Futher to my last message regarding samba being confused when a Word97
file was being saved.  I have been looking at the docs and log files
again and now understand that the problem is related to opportunistic
locking.  I also found the part of the log file that details the start
of the event.  Here it is:

1998/06/19 15:51:19 ukswi1000 (175.12.50.218) connect to service its as
user bramsons (uid=10808,gid=11000) (pid 25917)
check_file_sharing: NT redirector workaround - rename attempted on batch
oplocked file samba-tests/~WRD0000.tmp, dev = ff00061a, inode = 3b20b
check_file_sharing: NT redirector workaround - rename attempted on batch
oplocked file samba-tests/~WRD0002.tmp, dev = ff00061a, inode = 3b20d
can't open username map /usr/local/samba/etc/smbusers
1998/06/19 16:02:26 ukswi1000 (175.12.50.218) connect to service its as
user bramsons (uid=10808,gid=11000) (pid 26270)
1998/06/19 16:02:58 request_oplock_break: no response received to oplock
break request to pid 25917 on port 3273 for dev = ff00061a, inode 3b20d
1998/06/19 16:03:30 request_oplock_break: no response received to oplock
break request to pid 25917 on port 3273 for dev = ff00061a, inode 3b20d 
can't open username map /usr/local/samba/etc/smbusers
1998/06/19 16:03:41 ukswi1000 (175.12.50.218) connect to service its as
user bramsons (uid=10808,gid=11000) (pid 26308)

and so on.

Should I set oplocks = false ?   I'd prefer not to for performance
reasons.

Cheers,
-- 
Chris Stacey
Unix Systems Administrator, Motorola ECID
Tel: +44 (0)1793 565142  Fax: +44 (0)1793 565419
mailto: cstacey1@email.mot.com