mirror of
https://github.com/samba-team/samba.git
synced 2025-03-10 12:58:35 +03:00
6e27ff36b6
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
17 lines
840 B
XML
17 lines
840 B
XML
<samba:parameter name="posix locking"
|
|
type="boolean"
|
|
context="S"
|
|
xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
|
|
<description>
|
|
<para>
|
|
The <citerefentry><refentrytitle>smbd</refentrytitle> <manvolnum>8</manvolnum></citerefentry>
|
|
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). 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:parameter>
|