sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-08-04 08:22:08 +03:00
Code Activity

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

Browse Source 
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
This commit is contained in:
Kai Blin
2010-11-30 15:58:05 +01:00
parent bf9c3eedf8
commit 6e27ff36b6
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs-xml/smbdotconf/locking/posixlocking.xml
View File

@ -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>