On Wed, 2009-10-21 at 13:40 -0700, George Sanders wrote:
> I am tasked with pointing rsync transfers to valuable, live systems.
>
> The requirements include that this rsync job be run as root (rsync
> over ssh to the destination, as root) and that the --delete option be
> used.
> What would reall
I am tasked with pointing rsync transfers to valuable, live systems.
The requirements include that this rsync job be run as root (rsync over ssh to
the destination, as root) and that the --delete option be used.
The last piece is, the _remote_ destinations are not fixed - they are generated
f
On Tue 20 Oct 2009, Wayne Davison wrote:
> . I changed
> your ro, rw, and deny settings to be specified via suffixes. For
> example:
> auth user = joe:deny admin:rw @rsync:ro susan
Nice!
> Potential backward incompatibility: usernames used to be able to start
> with a @ and (surprisingly
On Wed, 2009-10-21 at 17:50 +0800, Thomas Gutzler wrote:
> is there a way to exclude files from being backed up when running rsync -b?
No. --backup is one of many rsync options for which per-file settings
might be useful but are not currently supported.
--
Matt
--
Please use reply-all for mos
Hello All
I have a rather curious problem. I rsync from a fileserver shared in via
cifs. This connection sometimes fails (don't worry, that is not the
question I have).
I am not at all sure where it goes wrong, but in the end the result is
that rsync thinks certain files has disappeared. It co
Hi,
is there a way to exclude files from being backed up when running rsync -b?
Let's assume the following file tree:
./src/f1
./src/temp/t1
./dest/src/f1
./dest/src/temp/t1
Now, I'm modifying both files f1 and t1 and run
rsync -a --relative -b --backup-dir=/backup/ src/ dest/
Both ./dest/src/f1 a
