The branch, master has been updated
via 6e27ff3 s3 docs: Reword posix locking text to answer a common
question
from bf9c3ee s3: Attempt to please autobuild
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit 6e27ff36b6b112d3b9eb6e4955b717190ab9fb0d
Author: Kai Blin <k...@samba.org>
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.
Autobuild-User: Kai Blin <k...@samba.org>
Autobuild-Date: Wed Dec 1 10:37:30 CET 2010 on sn-devel-104
-----------------------------------------------------------------------
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
