This does bring up one point though. Is there any way to optimize fileOnly by having a process which continuously monitors the relevant directory trees to maintain a list of the changed files.
list building? It seems like that turns into a huge bottleneck in the
"lots of files" situation.
In the case of Windows perhaps using the ReadDirectoryChangesW method.
http://msdn.microsoft.com/library/en-us/fileio/base/readdirectorychangesw.asp?frame=true
Otherwise scanning a large directory tree for changes is unavoidably slow. (At least it is only quick if you have very recently scanned the same tree and thus have all the directory data cached in memory.)
Mark Thornton
-- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
