> > But with inotify etc, it's possible to have already > > created a list of what's changed, and simply mirror the changes > > rather than doing the whole tree crawl. > > inotify will tell you which files have changed, but it won't tell you > what blocks of those files have changed - no? I don't remember. > > It's been a while since I looked at inotify, but the package for Linux > comes with a command line tool that sends notification messages to > STDOUT so you can use it in a script. A fairly simple script that > parses > out the file name and then calls cp or rsync on it ought to do it. For > a > bit more sophistication, add some code to delay processing by a few > minutes and batch the operations, so you don't end up repeatedly > mirroring the same file after every little write.
Huh - I didn't know inotify came with a text-based utility of its own. That sounds like it might be worth trying. Somebody else I asked came up with this, which is really cool: http://code.google.com/p/lsyncd/ _______________________________________________ bblisa mailing list [email protected] http://www.bblisa.org/mailman/listinfo/bblisa
