svn commit: samba-docs r955 - in trunk/smbdotconf/tuning: .
jra at samba.org
jra at samba.org
Fri May 19 00:35:26 GMT 2006
Author: jra
Date: 2006-05-19 00:35:25 +0000 (Fri, 19 May 2006)
New Revision: 955
WebSVN: http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=samba-docs&rev=955
Log:
Update to per-share parameter in 3.0.23.
Jeremy.
Modified:
trunk/smbdotconf/tuning/changenotifytimeout.xml
Changeset:
Modified: trunk/smbdotconf/tuning/changenotifytimeout.xml
===================================================================
--- trunk/smbdotconf/tuning/changenotifytimeout.xml 2006-05-12 21:39:31 UTC (rev 954)
+++ trunk/smbdotconf/tuning/changenotifytimeout.xml 2006-05-19 00:35:25 UTC (rev 955)
@@ -1,6 +1,6 @@
<samba:parameter name="change notify timeout"
type="integer"
- context="G"
+ context="S"
developer="1"
xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
<description>
@@ -10,7 +10,13 @@
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.</para>
+ 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>
More information about the samba-cvs
mailing list