summaryrefslogtreecommitdiff
path: root/docs/docbook/smbdotconf/tuning/strictsync.xml
diff options
context:
space:
mode:
authorAlexander Bokovoy <ab@samba.org>2003-04-06 22:14:01 +0000
committerAlexander Bokovoy <ab@samba.org>2003-04-06 22:14:01 +0000
commitc29eb90444170953721b087f8d26b4a3b98b3fe8 (patch)
tree257b1ee9b093a057b81e289fd511b992cc518642 /docs/docbook/smbdotconf/tuning/strictsync.xml
parent27aef6855f1543547b8190f06fd264d1b52a558d (diff)
downloadsamba-c29eb90444170953721b087f8d26b4a3b98b3fe8.tar.gz
samba-c29eb90444170953721b087f8d26b4a3b98b3fe8.tar.bz2
samba-c29eb90444170953721b087f8d26b4a3b98b3fe8.zip
Convert more parameters to new smb.conf(5) style. Document found occurences of non-documented parameters in doc-status
(This used to be commit 3a9784d8b2318af4d9b349edd1aba4065d25da23)
Diffstat (limited to 'docs/docbook/smbdotconf/tuning/strictsync.xml')
-rw-r--r--docs/docbook/smbdotconf/tuning/strictsync.xml44
1 files changed, 23 insertions, 21 deletions
diff --git a/docs/docbook/smbdotconf/tuning/strictsync.xml b/docs/docbook/smbdotconf/tuning/strictsync.xml
index b228f7cfcb..693806a503 100644
--- a/docs/docbook/smbdotconf/tuning/strictsync.xml
+++ b/docs/docbook/smbdotconf/tuning/strictsync.xml
@@ -1,23 +1,25 @@
-<samba:parameter xmlns:samba="http://samba.org/common">
- <term><anchor id="STRICTSYNC"/>strict sync (S)</term>
- <listitem><para>Many Windows applications (including the Windows
- 98 explorer shell) seem to confuse flushing buffer contents to
- disk with doing a sync to disk. Under UNIX, a sync call forces
- the process to be suspended until the kernel has ensured that
- all outstanding data in kernel disk buffers has been safely stored
- onto stable storage. This is very slow and should only be done
- rarely. Setting this parameter to <constant>no</constant> (the
- default) means that <citerefentry><refentrytitle>smbd</refentrytitle>
- <manvolnum>8</manvolnum></citerefentry> ignores the Windows applications requests for
- a sync call. There is only a possibility of losing data if the
- operating system itself that Samba is running on crashes, so there is
- little danger in this default setting. In addition, this fixes many
- performance problems that people have reported with the new Windows98
- explorer shell file copies.</para>
+<samba:parameter name="strict sync"
+ context="S"
+ xmlns:samba="http://samba.org/common">
+<listitem>
+ <para>Many Windows applications (including the Windows 98 explorer
+ shell) seem to confuse flushing buffer contents to disk with doing
+ a sync to disk. Under UNIX, a sync call forces the process to be
+ suspended until the kernel has ensured that all outstanding data in
+ kernel disk buffers has been safely stored onto stable storage.
+ This is very slow and should only be done rarely. Setting this
+ parameter to <constant>no</constant> (the default) means that
+ <citerefentry><refentrytitle>smbd</refentrytitle>
+ <manvolnum>8</manvolnum></citerefentry> ignores the Windows
+ applications requests for a sync call. There is only a possibility
+ of losing data if the operating system itself that Samba is running
+ on crashes, so there is little danger in this default setting. In
+ addition, this fixes many performance problems that people have
+ reported with the new Windows98 explorer shell file copies.</para>
- <para>See also the <link linkend="SYNCALWAYS"><parameter moreinfo="none">sync
- always&gt;</parameter></link> parameter.</para>
+ <para>See also the <link linkend="SYNCALWAYS"><parameter moreinfo="none">sync
+ always&gt;</parameter></link> parameter.</para>
- <para>Default: <command moreinfo="none">strict sync = no</command></para>
- </listitem>
- </samba:parameter>
+ <para>Default: <command moreinfo="none">strict sync = no</command></para>
+</listitem>
+</samba:parameter>