On Mon, Apr 23, 2001 at 06:57:14PM -0400, David Bolen wrote:
[very good reply to Randy Kramer deleted]
> > Aside: I think, based on your previous response, that if I did a
> > multifile rsync (say 60 files), and rsync was interrupted after 20
> > of the files were rsync'd, the --compare-dest option would work to
> > avoid rsync'ing the first 20 files and then rsync would rsync the
> > last 40 files in the normal manner (i.e., breaking them into blocks
> > of 3000 to 8000 bytes and then comparing them, and transferring only
> > the blocks that were different).
>
> I don't think the --compare-dest would be the reason rsync would skip
> the first 20 - it would just see them as existing in the target
> directory at the right date and size. Where --compare-dest could come
> into play was if they already existed in the separate comparision
> directory, in which case they wouldn't be transferred at all (unless
> you were using the -I option).
The only clarification I would add is to say that --compare-dest only comes
into play when a file does not exist in the target directory (which you
do imply in the first sentence but not in the second). Any time rsync
finds a file with a matching timestamp and size (when not using -I) in
either the target or compare-dest directory, it will skip the file. If
it finds a file that does not match the timestamp and size (looking first
in target, then in compare-dest), it will then apply the "rsync algorithm"
to that file and write output into the target directory.
- Dave Dykstra
