On Wed, Apr 22, 2015 at 10:17 AM, Kevin Korb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> No, even if bandwidth is your concern I would say that --checksum is
> wrong. Maybe if bandwidth is so scarse that a few KB vs a few MB
> equates to dollars then sure, use --checksum.
Yes, i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No, even if bandwidth is your concern I would say that --checksum is
wrong. Maybe if bandwidth is so scarse that a few KB vs a few MB
equates to dollars then sure, use --checksum. Otherwise, letting
rsync re-delta-xfer everything is certainly faster
On Wed, Apr 22, 2015 at 9:15 AM, Kevin Korb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Normally, I would say that --checksum is actually slower than just
> letting rsync re-copy everything
Depends on the network capacity and costs associated with that bandwidth :(
>and therefor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Normally, I would say that --checksum is actually slower than just
letting rsync re-copy everything and therefore is almost always the
wrong thing to do. However, in this case, you really don't want to
overwrite the running OS even with files that are
On Wed, Apr 22, 2015 at 1:03 AM, James Moe wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
> opensuse 13.2
> linux v3.16.7-7-desktop x86_64
> rsync v3.1.1
>
> I used rsync to copy /usr/ to another volume with these options:
> - --recursive --one-file-system --links --st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
First, make note that in the future always run rsync with at least
either --times or --archive. If you had used --archive you would be
fine and if you had used --times then rsync could just fix the
permissions and ownerships (you would want to dry run
