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/tuning/aiowritebehind.xml | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 docs-xml/smbdotconf/tuning/aiowritebehind.xml

(limited to 'docs-xml/smbdotconf/tuning/aiowritebehind.xml')

diff --git a/docs-xml/smbdotconf/tuning/aiowritebehind.xml b/docs-xml/smbdotconf/tuning/aiowritebehind.xml
new file mode 100644
index 0000000..d60af71
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/aiowritebehind.xml
@@ -0,0 +1,24 @@
+<samba:parameter name="aio write behind"
+                 context="S"
+		 type="string"
+                 substitution="1"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+	<para>If Samba has been built with asynchronous I/O support,
+	Samba will not wait until write requests are finished before returning
+	the result to the client for files listed in this parameter.
+	Instead, Samba will immediately return that the write
+	request has been finished successfully, no matter if the
+	operation will succeed or not. This might speed up clients without
+	aio support, but is really dangerous, because data could be lost
+	and files could be damaged.
+	</para>
+	<para>
+	The syntax is identical to the <smbconfoption name="veto files"/>
+	parameter.
+	</para>
+</description>
+
+<value type="default"/>
+<value type="example">/*.tmp/</value>
+</samba:parameter>
-- 
cgit v1.2.3