From 6f5133aa825572d5b4e12d9c23f8040259798660 Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Wed, 10 Sep 2003 01:14:37 +0000 Subject: merge from 3.0 (This used to be commit fa0d4ea150e0243958273168eaf9bf195e2c12e0) --- docs/docbook/smbdotconf/locking/strictlocking.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/docbook/smbdotconf/locking') diff --git a/docs/docbook/smbdotconf/locking/strictlocking.xml b/docs/docbook/smbdotconf/locking/strictlocking.xml index 34c1c7fe5e..a13b4d52a1 100644 --- a/docs/docbook/smbdotconf/locking/strictlocking.xml +++ b/docs/docbook/smbdotconf/locking/strictlocking.xml @@ -3,15 +3,15 @@ xmlns:samba="http://samba.org/common"> This is a boolean that controls the handling of - file locking in the server. When this is set to yes + 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 no the server does file + 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 + is important. So in the vast majority of cases, strict locking = no is preferable. Default: strict locking = no -- cgit