From ef74f0f9b14736d9c134a0bb54f2e1ae91c4d616 Mon Sep 17 00:00:00 2001 From: Karolin Seeger Date: Mon, 30 Nov 2009 13:34:34 +0100 Subject: [PATCH] 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) --- docs-xml/smbdotconf/tuning/aiowritebehind.xml | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 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 00000000000..c88cd97fa97 --- /dev/null +++ b/docs-xml/smbdotconf/tuning/aiowritebehind.xml @@ -0,0 +1,23 @@ + + + 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. + + + The syntax is identical to the + parameter. + + + + +/*.tmp/ + -- 2.11.4.GIT