-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jay Sprenkle wrote: > I've heard this too. Windows networking has some issues with locking. > You might research 'oplocks' or 'opportunistic locking' (or > opportunistic caching) > if you're interested in understanding what it's doing. I was reading > it the other > day and thought it might be the key to making it work correctly if you > could > turn oplocks off in windows.
Oplocks do not break things. Oplocks will guarantee consistency. They are granted when only one client OS has a file open letting that client OS perform locking and caching operations internally without consulting the server each time. If another client wants to open the file, then that second open request is held up by the server, the first client contacted and asked to flush any outstanding data, acquire locks, and drop the oplock. Once that has happened then the second client gets the answer to its open request. There are other forms of oplocks that allow for opening and closing the file multiple times without consulting the server as well as some forms of limiting sharing (dropped when clients start using byte range locking). There have been some problems with Windows when smb signing is in use as the design of smb signing assumes request response pairs whereas oplock break notifications are asynchronous. Other than degenerate cases, current Windows versions have been patched. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFpF+kmOOfHg372QQRAsUXAJ0WDnN/+L2EUO4Yp04eyo6XJU3a+QCg1Egd 81HnIn2KLf0QKyTlYsQIg3g= =DccF -----END PGP SIGNATURE----- ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
