From 8daa83a594a2e98f39d764422bfbdbc62c9efd44 Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Fri, 19 Apr 2024 19:20:00 +0200
Subject: Adding upstream version 2:4.20.0+dfsg.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 docs-xml/smbdotconf/locking/posixlocking.xml | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 docs-xml/smbdotconf/locking/posixlocking.xml

(limited to 'docs-xml/smbdotconf/locking/posixlocking.xml')

diff --git a/docs-xml/smbdotconf/locking/posixlocking.xml b/docs-xml/smbdotconf/locking/posixlocking.xml
new file mode 100644
index 0000000..f38b2bd
--- /dev/null
+++ b/docs-xml/smbdotconf/locking/posixlocking.xml
@@ -0,0 +1,17 @@
+<samba:parameter name="posix locking"
+                 type="boolean"
+                 context="S"
+                 parm="1"
+                 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>
-- 
cgit v1.2.3