From 1cd7864412a1708fd968d39d52431f7632ddf3cd Mon Sep 17 00:00:00 2001 From: Volker Lendecke Date: Mon, 19 Feb 2007 13:53:54 +0000 Subject: After merging the notify stuff to 3_0_25, check in the docs (This used to be commit ee532da6c8eb7c21937702e942e2755cf0aac042) --- docs/smbdotconf/tuning/changenotifytimeout.xml | 24 ------------------------ 1 file changed, 24 deletions(-) delete mode 100644 docs/smbdotconf/tuning/changenotifytimeout.xml (limited to 'docs/smbdotconf/tuning') 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 @@ - - - This SMB allows a client to tell a server to - "watch" 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 smbd - 8 daemon only performs such a scan - on each requested directory once every change notify - timeout 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. - - -60 -300Would change the scan time to every 5 minutes. - -- cgit