s3:docs: Document "aio write behind".

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

Karolin
(cherry picked from commit fde7c2ab19bc7442d8ee9d85ab2fe54e0cfb4782)
(cherry picked from commit 267ebc03b43dd8c11f5aebf341620b0d94d95135)
(cherry picked from commit 93bbbd3cc776e4aa69239cb086067ec953fc8c8e)
(cherry picked from commit 65a3f18ccd9aa8b4ec31e9e7e5465631ee53afca)

diff --git a/docs-xml/smbdotconf/tuning/aiowritebehind.xml b/docs-xml/smbdotconf/tuning/aiowritebehind.xml
new file mode 100644 (file)
index 0000000..c88cd97
--- /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>