Wayne, I notice that .rsyncsums is starting to look a lot like the index that the git version control system ( http://git.or.cz/ ) uses to determine whether a file has changed since it was last staged for committing. The git index has been heavily used and tested, so you might find it helpful when implementing a checksum cache for rsync. Specifically, it has protection against being fooled when a file's checksum is cached and the file is modified again in the same second; .rsyncsums could use this.
I think it would be even better to factor out logic for caching file checksums into a separate library used by both rsync and git. This would have two advantages: the subtleties of implementing a 100% correct cache only have to be addressed once, and different programs can make use of each other's cached checksums. GNU make and Beagle desktop search might also use the library. Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
