change oplock contention limit because corruption?
rschott at schott-memsys.com
Mon Nov 27 18:17:47 GMT 2000
ahhh!! obviously I found what I was searching for:
oplock break wait time (G)
This is a tuning parameter added due to bugs in both Windows 9x and WinNT.
If Samba responds to a client too quickly when that client issues an SMB...
DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA
My question, now: does it hurt to set
Default: oplock break wait time = 10
to 20 ms?
anyone experimented, here?
> Is there anybody in the list who can tell me the influence of the
> oplock contention limit to control the locking behaviour on a shared
> We have one file that is opened for write ops from several wkstations.
> It showed, that this file is being corrupted after some write ops.
> It has been told by the software manufacturer that they had under *some*
> conditions similar behaviour with a Novell server. They had to disable the
> write cache, there.
> Is it possible to slow the server so it behaves like a - sorry - weird
> Novell or NT box?
More information about the samba