search for: rsyncsums

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 fo...

This is a suggestion for adding to rsync an option "--checksum-path=PROGRAM". Once this option is given, provided it is accompained by option "--checksum", both the receiving and sending side of rsync would compute checksums calling PROGRAM, instead of the usual checksum program. Why is this usefull? Suppose I have two collections of MP3 files at different locations which I

Hi, as scanning large repositories for each client connection causes unnecessary CPU/IO load, I want to know if is it possible to generate checksum digest files on the server, meanwhile? Best regards, Renne

Hi everyone! I played around with rsync sources a little and wrote a small patch that computes the checksums from parts of the files only. I'm just writing to ask if the rsync developers would have any interest in the sort of functionality described below. If you do, I'm willing to work with you to produce a cleaned up patch for git. For background: This started as a way to satisfy an

Overview -------- I am trying to use --ignore-times with --link-dest and find that all files are duplicated inappropriately (IMHO). I think it is because --link-dest creates a hard link, which results in the link count, and so Change Time, changing. This requires rsync to create a new inode and duplicate the data just to preserve the ctime. If --ignore-times is not specified, only mtime and the