Yes, I knew --force made a difference when not using --delete (that's
very much like the example in the message I referred to), and I think
it's good that way and --force should not be the default without --delete.
I thought you were using --delete. If --force makes a difference in any
case that -
Dave Dykstra wrote:
Could you please post your full command line and say where in the directory
structure the directories were replaced by symlinks? I have not yet been
able to come up with an example where --force makes a difference when
using --delete and -r (or -a). Refer to
http://lists.
On Mon, Jan 06, 2003 at 08:36:35AM -0700, David Garamond wrote:
> John Van Essen wrote:
> >Dave,
> >
> >What you need is the --force option. It's not obvious from the
> >all-too-generic name, but that will do the trick.
> >
> >To the rsync maintainers - this is somewhat of an FAQ. Perhaps
> >the
John Van Essen wrote:
Dave,
What you need is the --force option. It's not obvious from the
all-too-generic name, but that will do the trick.
To the rsync maintainers - this is somewhat of an FAQ. Perhaps
the error message could also say '(see the --force option)' to
help users discover the sol
On Mon, Jan 06, 2003 at 02:05:47AM -0600, John Van Essen wrote:
> Dave,
>
> What you need is the --force option. It's not obvious from the
> all-too-generic name, but that will do the trick.
>
> To the rsync maintainers - this is somewhat of an FAQ. Perhaps
> the error message could also say '(
Dave,
What you need is the --force option. It's not obvious from the
all-too-generic name, but that will do the trick.
To the rsync maintainers - this is somewhat of an FAQ. Perhaps
the error message could also say '(see the --force option)' to
help users discover the solution more easily.
--
just to correct myself: this has nothing to do with rdiff-backup (which
uses *rdiff*, not rsync). local backups with the rdiff-backup tool are
fine. the problem is with rsync, when we are trying to mirror the local
backups to another machine using rsync.
David Garamond wrote:
our daily backup i
nope, --delete-after didn't seem to resolve the problem. what's needed
is apparently for rsync to do an "rm -r oldname1" instead of "rmdir
oldname1".
Eric Whiting wrote:
I have observed this same problem. Are you running --delete-after? I
assumed it might be related to that option.
eric
David
I have observed this same problem. Are you running --delete-after? I
assumed it might be related to that option.
eric
David Garamond wrote:
>
> our daily backup is done using the rdiff-backup tool, which in turn
> utilizes rsync/librsync to do the actual mirroring work.
>
> a few days ago
our daily backup is done using the rdiff-backup tool, which in turn
utilizes rsync/librsync to do the actual mirroring work.
a few days ago we did a refactoring and renamed a bunch of directories.
for backward compatibility we maintain the old names by symlinking it to
the new names. so, for ex
10 matches
Mail list logo
