From 6b5c92603c3c6738cf9b8b974da5fad6226914b7 Mon Sep 17 00:00:00 2001 From: Jeremy Allison Date: Mon, 17 Apr 2006 22:35:57 +0000 Subject: Document default change from "yes" to "auto". Jeremy. (This used to be commit 66f046b6390302472b5e377478913ce971eee3bf) --- docs/smbdotconf/locking/strictlocking.xml | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/docs/smbdotconf/locking/strictlocking.xml b/docs/smbdotconf/locking/strictlocking.xml index 0394e24b28..4aa337cc93 100644 --- a/docs/smbdotconf/locking/strictlocking.xml +++ b/docs/smbdotconf/locking/strictlocking.xml @@ -1,22 +1,29 @@ - This is a boolean that controls the handling of file locking in the server. When this is set to yes, + This is an enumberated type that controls the handling of file locking in the server. When this is set to yes, the server will check every read and write access for file locks, and deny access if locks exist. This can be slow on some systems. + + When strict locking is set to Auto (the default), the server performs file lock checks only on non-oplocked files. + As most Windows redirectors perform file locking checks locally on oplocked files this is a good trade off for + inproved performance. + + When strict locking is disabled, the server performs file lock checks only when the client explicitly asks for them. Well-behaved clients always ask for lock checks when it is important. So in the vast majority of cases, + strict locking = Auto or strict locking = no is acceptable. -yes +Auto -- cgit