[Samba] oplock problem on NTUSER.DAT (fwd)
rashkae at tigershaunt.com
Tue Jul 29 23:41:41 GMT 2003
---------- Forwarded message ----------
Date: Tue, 29 Jul 2003 19:40:48 -0400 (EDT)
From: Rashkae <rashkae at tigershaunt.com>
To: Marco De Vitis <starless at despammed.com>
Subject: Re: [Samba] oplock problem on NTUSER.DAT
Try to veto oplocks for that file.
In the global section of your smb.conf, add the following
veto oplock files = /NTUSER.DAT/
Let us know if that changes the behaviour.
This sounds like an interseting quirk in the W2K clients.
Jul 29 7:39pm
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 Wed, 30 Jul 2003, Marco De Vitis wrote:
I'm on a network with a Samba 2.2.8a fileserver + PDC (Mandrake Linux
9.0) and various Win2000 Pro clients.
Very often, when I log off from one client and log on a different one
soon after, I get an error message telling me that the remote profile
cannot be loaded, and the local one will be used, as if the profile was
still locked by the previous session.
One peculiar thing to notice is that, if I logon simultaneously on two
or more clients, I do not get any similar errors, everything works fine.
In syslog I found the following lines:
[2003/07/29 18:53:43, 0] smbd/oplock.c:oplock_break(797)
oplock_break: receive_smb timed out after 30 seconds.
oplock_break failed for file mdv/NTUSER.DAT (dev = 307, inode =
449101, file_id = 2965).
[2003/07/29 18:53:43, 0] smbd/oplock.c:oplock_break(869)
oplock_break: client failure in oplock break in file mdv/NTUSER.DAT
I did not set any option regarding oplocks in my smb.conf, I'm using the
defaults in this regard.
Can I work around the problem by using some particular smb.conf options,
or is it an unavoidable Win2000 client problem?
..."Skylarking", XTC 1986
To unsubscribe from this list go to the following URL and read the
More information about the samba