summaryrefslogtreecommitdiff
path: root/docs/smbdotconf/tuning/changenotifytimeout.xml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/smbdotconf/tuning/changenotifytimeout.xml')
-rw-r--r--docs/smbdotconf/tuning/changenotifytimeout.xml24
1 files changed, 0 insertions, 24 deletions
diff --git a/docs/smbdotconf/tuning/changenotifytimeout.xml b/docs/smbdotconf/tuning/changenotifytimeout.xml
deleted file mode 100644
index c450a173d8..0000000000
--- a/docs/smbdotconf/tuning/changenotifytimeout.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-<samba:parameter name="change notify timeout"
- type="integer"
- context="S"
- developer="1"
- xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
-<description>
- <para>This SMB allows a client to tell a server to
- &quot;watch&quot; a particular directory for any changes and only reply to
- the SMB request when a change has occurred. Such constant scanning of
- a directory is expensive under UNIX, hence an <citerefentry><refentrytitle>smbd</refentrytitle>
- <manvolnum>8</manvolnum></citerefentry> daemon only performs such a scan
- on each requested directory once every <parameter moreinfo="none">change notify
- timeout</parameter> seconds. Note that in 3.0.23 this has been changed to a
- per-share parameter and setting this to zero prevents any change notify directory
- scans completely on a share. This is to allow this paramter to be set to zero on
- shares configured for very large directories, where a Windows client will re-scan
- the entire directory after every delete operation (when deleting many files) due to
- the change notify triggering. This is an extremely expensive operation on some
- systems.</para>
-</description>
-
-<value type="default">60</value>
-<value type="example">300<comment>Would change the scan time to every 5 minutes.</comment></value>
-</samba:parameter>