The branch, v3-6-test has been updated
via 8268e03 s3 docs: Reword posix locking text to answer a common
question
from e6d3146 s3: Fix bug 7832
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=v3-6-test
- Log -----------------------------------------------------------------
commit 8268e030235b6cb5e6288a53133bba1faa9e63b1
Author: Kai Blin <[email protected]>
Date: Tue Nov 30 15:58:05 2010 +0100
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.
(cherry picked from commit fd17979293ecb37bdb16c5078fefb3f63cfb3730)
-----------------------------------------------------------------------
Summary of changes:
docs-xml/smbdotconf/locking/posixlocking.xml | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
Changeset truncated at 500 lines:
diff --git a/docs-xml/smbdotconf/locking/posixlocking.xml
b/docs-xml/smbdotconf/locking/posixlocking.xml
index e5a89f5..25476f0 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>
--
Samba Shared Repository
