From: Karolin Seeger <kseeger@samba.org>
Date: Mon, 30 Nov 2009 12:34:34 +0000 (+0100)
Subject: s3:docs: Document "aio write behind".
X-Git-Url: http://git.samba.org/?a=commitdiff_plain;h=fde7c2ab19bc7442d8ee9d85ab2fe54e0cfb4782;p=metze%2Fsamba%2Fwip.git

s3:docs: Document "aio write behind".

Part of a fix for bug #6890 (Some smb.conf parameters are undocumented).

Karolin
---

diff --git a/docs-xml/smbdotconf/tuning/aiowritebehind.xml b/docs-xml/smbdotconf/tuning/aiowritebehind.xml
new file mode 100644
index 000000000000..c88cd97fa970
--- /dev/null
+++ b/docs-xml/smbdotconf/tuning/aiowritebehind.xml
@@ -0,0 +1,23 @@
+<samba:parameter name="aio write behind"
+                 context="S"
+		 type="string"
+                 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>