On Tue, 2 Aug 2011, Kevin Korb wrote:
> 1. Update rsync. You are MANY years out of date. Updating rsync is not
> going to break whatever obsolete other stuff you are running.
Not an option in this case, but thank you for the suggestion anyway :)
> 2. If you are rsyncing from / --relative doe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
3 things...
1. Update rsync. You are MANY years out of date. Updating rsync is not
going to break whatever obsolete other stuff you are running.
2. If you are rsyncing from / --relative doesn't do anything.
3. --delete is aborted if almost any err
Hi,
We back up a lot of machines with varying version of rsync installed on
them. The oldest machine (hopefully soon to be retired) is running rsync
version 2.5.7 (protocol version 26).
We back this machine up from "/" onwards with a few excludes in there. I
noticed today that whenever we use
https://bugzilla.samba.org/show_bug.cgi?id=8342
--- Comment #1 from Christopher Key 2011-08-02 19:02:32 UTC
---
Created attachment 6748
--> https://bugzilla.samba.org/attachment.cgi?id=6748
patch described in bug 8342
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
-
https://bugzilla.samba.org/show_bug.cgi?id=8342
Summary: rsync can't handle populate dirs without u+rx
permissions
Product: rsync
Version: 3.0.9
Platform: All
OS/Version: All
Status: NEW
Severity: normal
I've a script which calls:
rsync --password-file=password.txt rsync://server/files /files
However, due to an unrelated error password.txt was missing.
In authenticate.c:auth_client, the code tries to read from the password file,
then tries the RSYNC_PASSWORD env var, then calls getpass(3). This
