My workplace provides access to a networked drive to store files/folders so they will be backed up. Each user sees it as the 'H' drive, but each user sees only their own files. The DocFetch daemon tracks changes to files saved on the local 'C' drive, but I must manually update the index to update 'H' drive index information. So, it would be useful if the daemon tracked all changes, not just those on local drive files. JRS
I've googled about this a bit and found that other file monitoring applications basically have the same problem: There's simply no way to (efficiently) detect file changes on network drives, because the network drives themselves don't send any change notifications. So I'm afraid there's not much we can do here... :(
Hi. I too am very keen on such a feature. As a workaround DocFetcher could automatically run index-refreshes for network drives at regular intervalls. Once a day would suffice for my taste, as usually I only need to find things I put somewhere a couple days/weeks ago.
As for the change detection: there are various backup-tools that are pretty good at comparing files on my harddisk with the backup folder on the networkdrive and, in case of new/renewed files, automatically backing them up (currently I'm using synctoy..). Maybe the routine of this file comparison could be used to detect filechanges for docfetcher too???
In any case it would be great if DocFetcher would somehow show to the user, when an index has been updated last time and why it doesn't happen automagically on network drives (explanation in helpfile?).
Thanks for the great tool!
Good point. The indexing at regular intervals seems to be a nice thing to have. We'll see if we can implement this someday...
For now, I hope the F5 button will suffice :)