From 89771b45bb0bd86a6a2a70fe0f03b2560358dddd Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Wed, 10 Sep 2003 00:49:14 +0000 Subject: fix some typos (This used to be commit 6d46fcdaf037a3dd42ea2883f9c518f72bb9d8a8) --- docs/docbook/smbdotconf/locking/strictlocking.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/docbook/smbdotconf/locking/strictlocking.xml b/docs/docbook/smbdotconf/locking/strictlocking.xml index 34c1c7fe5e2..a13b4d52a1c 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