summaryrefslogtreecommitdiff
path: root/docs/docbook/smbdotconf/tuning/strictsync.xml
blob: b228f7cfcb4974994dc94a23d685f1e01917e307 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
<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>

		<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>