search for: axhax

...skip based on checksum, not mod-time & size -n, --dry-run perform a trial run with no changes made Can I use these to, in effect, check all of my backup files for integrity? Please note that the options I have been using to make my backups are as follows: -v -t -axHAXS --delete --fileflags --force-change I don't imagine that either the -n or -c options will interact badly with any of those, correct? Regards, rfg

I've been getting spurious unnecessary copying of files on OSX when using the crtimes patch and the --crtimes -H options (version 3.0.4). I can reliably demonstrate it (on OSX 10.5) by doing this several times (as root): rsync -v -N -axHAX --delete-during --fileflags --force-change /usr/ bin/ /tmp/foo/ I think I've tracked it down to the hard-link processing code in recv_file_entry() in flist.c around line 751: Essentially, all hard links but the first will get their modtime set correctly (from first->modtime), but...

...me & > size -n, --dry-run perform a trial run with no > changes made > > Can I use these to, in effect, check all of my backup files for > integrity? > > Please note that the options I have been using to make my backups > are as follows: > > -v -t -axHAXS --delete --fileflags --force-change > > I don't imagine that either the -n or -c options will interact > badly with any of those, correct? > > > Regards, rfg > - -- ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._...