Backuppc uses rsync (do not know what rsync version but Backuppc is
latest version, so assuming 'very' current rsync version is included)
and I am trying to add acl and attr file permissions to rsync in
RsyncArgs and RsyncRestoreArgs and have discovered that their
addition is not that easy.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Both systems would need to have an rsync installed that support those
features. They are a compile time choice and are automatically
disabled if dependencies aren't met. You can see if they are
supported with 'rsync --version'. If they are
Thanks for your advice. I'll go back and read up on the options again.
---
-
Bob Wooden of Donelson Trophy
615.885.2846 (main)
www.donelsontrophy.com [1]
Everyone deserves an award!!
On 2015-06-25 09:41, Kevin Korb wrote:
-BEGIN PGP SIGNED MESSAGE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The command line order shouldn't matter though that might depend on
what else is in there (especially -s).
Rsync is backwards compatible so the version mismatch shouldn't matter
but 3.1 has some nice benefits over 3.0.9 so upgrading is a good idea.
Thank you. This helps get me closer.
One machine shows rsync 3.0.9 and the other shows rsync 3.1.0. Running
rsync --version both show ACL, xattr are supported.
Two questions, would the two different version cause it to fail?
Second, does the order rsync receives the switches matter. Does
I have a local directory that I am trying to sync with a remote directory.
That's fine, but there's a lot of data that is out of sync so I decided to make
a local copy of the difference to then bring to the remote location.
So I ran a dry-run between the two to generate a list of files in
