From 992f1e6b8f86b346fddd266b04d29cde69585633 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Wed, 7 Apr 2004 10:15:11 +0000 Subject: Add all the source files from the old CVS tree, add the 5 missing chapters from the HOWTO and add jht's Samba by Example book. (This used to be commit 9fb5bcb93e57c5162b3ee6f9c7d777dc0269d100) --- docs/smbdotconf/tuning/strictsync.xml | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 docs/smbdotconf/tuning/strictsync.xml (limited to 'docs/smbdotconf/tuning/strictsync.xml') diff --git a/docs/smbdotconf/tuning/strictsync.xml b/docs/smbdotconf/tuning/strictsync.xml new file mode 100644 index 0000000000..1d123cfe9c --- /dev/null +++ b/docs/smbdotconf/tuning/strictsync.xml @@ -0,0 +1,24 @@ + + + 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 no (the default) means that + smbd + 8 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. + + +sync always +no + -- cgit