[Samba] request_oplock_break: no response received to oplock break request

[Rashkae]

Nope, this has nothing to do with user owned processes.  What this does,
mean, however, is that the users are trying to share the files with
multiple computers with oplocks enabled.  You should search this mailing
list archive for discussions ad-nauseum about oplocks.

____________________________________________
Jan 13  1:56pm


They hang the man and flog the woman
That steal the goose from off the common,
But let the greater villain loose
That steals the common from the goose.
  --English folk poem, circa 1764








On Mon, 13 Jan 2003, toby bluhm wrote:

Hello,

I've been running samba 2.0.7 for a couple years now on a DEC alpha with
Tru64 4.0D. I't pertty much a default smb.conf as far as oplocks & that
sort of stuff.

Anyway, the other day some users started having troubles with saving
ms-word files. The smbd processes have always been running as root. But
now the users with the problem own their smbd process. And they get
errors like such in the log file:

   for dev = 8100000, inode = 17169, tv_sec = 3e22d418, tv_usec = 931fe
[2003/01/13 12:46:27, 0] smbd/oplock.c:(1204)
   request_oplock_break: no response received to oplock break request to
pid 5755 on port 1450 for dev = 8100000, inode = 144022
   for dev = 8100000, inode = 144022, tv_sec = 3e22dc57, tv_usec = d9670
[2003/01/13 12:46:30, 0] smbd/oplock.c:(1204)
   request_oplock_break: no response received to oplock break request to
pid 4265 on port 1395 for dev = 8100000, inode = 17312
   for dev = 8100000, inode = 17312, tv_sec = 3e22d418, tv_usec = 887d2
[2003/01/13 12:46:30, 0] smbd/oplock.c:(1204)
   request_oplock_break: no response received to oplock break request to
pid 5755 on port 1450 for dev = 8100000, inode = 144022
   for dev = 8100000, inode = 144022, tv_sec = 3e22dc57, tv_usec = d9670


It seems since some of the smbd processes is owned by root, the process
owned by the users cannot control the root owned process. Is this a
correct assumption? How or why would it start doing this? And the user
will have several smbd processes started in their name. Seems to be only
NT4 clients, although I've not verified that yet.

The only recent change I made was the IP address of the server. The
client have had their new IPs for some time now. I'm not tying samba to
any specific interface or IP.

ANy clues as to how to fix this?


Thanks


-tkb

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba