s3 docs: Reword posix locking text to answer a common question

vl recently pointed me to a valid reason to use posix locking = no.
Fix the smb.conf manpage to explain this reason, as this question
comes up on the samba mailing list from time to time as well.

Autobuild-User: Kai Blin <kai@samba.org>
Autobuild-Date: Wed Dec  1 10:37:30 CET 2010 on sn-devel-104

diff --git a/docs-xml/smbdotconf/locking/posixlocking.xml b/docs-xml/smbdotconf/locking/posixlocking.xml
index e5a89f59aafc181e54532c87a520ca12494a3818..25476f09b413c1c518bebbb2b6f9b0f7d51c4131 100644 (file)
--- a/docs-xml/smbdotconf/locking/posixlocking.xml
+++ b/docs-xml/smbdotconf/locking/posixlocking.xml
@@ -8,7 +8,8 @@
        daemon maintains an database of file locks obtained by SMB clients. The default behavior is 
        to map this internal database to POSIX locks. This means that file locks obtained by SMB clients are 
        consistent with those seen by POSIX compliant applications accessing the files via a non-SMB 
-       method (e.g. NFS or local file access). You should never need to disable this parameter.
+       method (e.g. NFS or local file access). It is very unlikely that you need to set this parameter
+       to "no", unless you are sharing from an NFS mount, which is not a good idea in the first place.
        </para>
 </description>
 <value type="default">yes</value>