Oplock strange message

eperez at consultant.com eperez at consultant.com
Mon Oct 29 16:04:02 GMT 2001


Sirs, several computers in our network are begining to exhibit the
following erros in the /var/log/samba/log.machine_name.
I am running Samba that comes with Mandrake 8.0

The error is:

[2001/10/29 19:05:37] smbd/oplock.c:request_oplock_break (1244)
request_oplock_break: no response received to oplock break request to pid
981 on port 32780 for dev = 301, inode = 291068

for dev = 301, inode = 291068, tv_sec = 3bdddbcb, tv_usec = 94d66


This messages are repeated almost every second in our 40 node logs.
This message started to appear about two days ago. Nothing has been
changed in the samba.

The error gets corrected (i mean the users are able to access the file
again) when I do a samba stop/samba start.

the samba is being used to share a single file used to keep track of a
time based program.

Here is smb.conf
[global]
workgroup = SKY
netbios name = STIMPY
server string = Samba Sever %v
interfaces = 192.168.0.1/255.255.255.0 127.0.0.1/255.255.255.0
bind interfaces only = yes
security = share
encrypt passwords = yes
null passwords = yes
log file = /var/log/samba/log.%m
mx log size = 50
time server = yes
read prediction = yes
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=16384
SO_RCVBUF=16384
printcap name = lpstat
os level = 65
lm announce = false
preferred master = yes
domain master = yes
dns proxy = no
wins support = yes
auto services = entermex
default service = entermex
socket address = 192.168.0.1
printing = cups

[entermex]
path = /home/entermex
guest account = root
force user = root
force group = root
writeable = yes
guest only = yes
guest ok = yes

[base$]
path = /home/entermex
guest account = root
force user = root
force group = root
writeable = yes
guest only = yes
guest ok = yes
browseable = no


That's it. Thats all the smb.conf. I know it is not the most security
minded file share on earth, but as i said, it only share a single file for
a clumsy time sharing program that runs on windows machines (all 40
clients).

Any suggestions will be appreciated.

thanks,
Erick






More information about the samba mailing list