summaryrefslogtreecommitdiff
path: root/docs-xml/smbdotconf/locking
diff options
context:
space:
mode:
authorKai Blin <kai@samba.org>2010-11-30 15:58:05 +0100
committerKai Blin <kai@samba.org>2010-12-01 10:37:30 +0100
commit6e27ff36b6b112d3b9eb6e4955b717190ab9fb0d (patch)
tree56cf305f06686cd5ee8d67697c27320a5ac77324 /docs-xml/smbdotconf/locking
parentbf9c3eedf834e5637a23f051e0c8db6687c6dcf1 (diff)
downloadsamba-6e27ff36b6b112d3b9eb6e4955b717190ab9fb0d.tar.gz
samba-6e27ff36b6b112d3b9eb6e4955b717190ab9fb0d.tar.bz2
samba-6e27ff36b6b112d3b9eb6e4955b717190ab9fb0d.zip
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
Diffstat (limited to 'docs-xml/smbdotconf/locking')
-rw-r--r--docs-xml/smbdotconf/locking/posixlocking.xml3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs-xml/smbdotconf/locking/posixlocking.xml b/docs-xml/smbdotconf/locking/posixlocking.xml
index e5a89f59aa..25476f09b4 100644
--- 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>