Which sounds like it's not obeying the rules of rsync in just test: without --upadte, you _always_ transfer all files, no matter what. For my taste, there is a golden rule for aegir platforms: - Dont touch them by hand!- Never change a platform - rather create a new one and migrate If you think --update is not the best for the broad users ( i expect it thiouh ), we could simply take it in as a configuration? So people could activate compress or other stuff (if needed). -u, --update This forces rsync to skip any files which exist on the destination and have a modified time that is newer than the source file.
This does mean that this option is only looking at the existing files in the destination hierarchy itself.
(If an existing destination file has a modification time equal to the source files, it will be updated if the sizes are different.) Note that this does not affect the copying of symlinks or other special files.
Also, a difference of file format between the sender and receiver is always considered to be important enough for an update, no matter what date is on the objects.
WELL, I thought, maybe it is wasting CPU time doing unnecessary refreshes. This is normally 0 (for an exact match), but you may find it useful to set this to a larger value in some situations.
In particular, when transferring to or from an MS Windows FAT filesystem (which represents times with a 2-second resolution), --modify-window=1 is useful (allowing times to differ by up to 1 second).