[Samba] oplock_break messages in logs after 2.2.5 upgrade

[drenning, bruce]

Since I upgraded my servers from 2.0.10 to 2.2.5, I am gettting messages
logged about oplock_break failures. Can I just ignore these? Nobody has
reported any difference in performance. I haven't changed the default
logging level in smb.conf, can I change it so it ignores these messages w/o
missing something else important?



Aug  5 12:10:34 files smbd[5775]: [2002/08/05 12:10:34, 0]
smbd/oplock.c:oplock_break(796) 
Aug  5 12:10:34 files smbd[5775]:   oplock_break: receive_smb timed out
after 30 seconds. 
Aug  5 12:10:34 files smbd[5775]:   oplock_break failed for file Diocese/CRS
donor counts per US diocese.xls (dev = 809, inode = 474562, file_id = 147). 
Aug  5 12:10:34 files smbd[5775]: [2002/08/05 12:10:34, 0]
smbd/oplock.c:oplock_break(868) 
Aug  5 12:10:34 files smbd[5775]:   oplock_break: client failure in oplock
break in file Diocese/CRS donor counts per US diocese.xls 
Aug  5 12:10:34 files smbd[5775]: [2002/08/05 12:10:34, 0]
smbd/reply.c:reply_lockingX(4489) 
Aug  5 12:10:34 files smbd[5775]:   reply_lockingX: Error : oplock break
from client for fnum = 8771 and no oplock granted on this file (Diocese/CRS
donor counts per US diocese.xls).