Hi,
I've got one thats really stumping me... rsync 2.6.9 from FreeBSD
ports on both ends.
/usr/local/tmp/rsync --dry-run -v -v -v -v -v -v -v -v -v -v -v -v --dry-run
-vrlptHDgozxS --partial --force --delete --numeric-ids --exclude='A/*'
--include='*/' /usr/local/etc/machines/ [EMAIL
>
> On Sat, Feb 02, 2008 at 08:12:20PM -0500, Tuc at T-B-O-H.NET wrote:
> > /usr/local/tmp/rsync --dry-run -v -v -v -v -v -v -v -v -v -v -v -v
> > --dry-run -vrlptHDgozxS --partial --force --delete --numeric-ids
> > --exclude='A/*' --include='*/' /u
Hi,
Wouldn't you know, I can't get rsync to throw an error during
a copy. :) I need to put together some instructions for a guy that runs
a WISP for him to look over before weekly backups are made (I'll be
copying the files to /dev/null so any read errors can be caught).
I can do
> On Fri, 2008-05-30 at 12:16 -0400, Tuc at T-B-O-H.NET wrote:
> > Wouldn't you know, I can't get rsync to throw an error during
> > a copy. :) I need to put together some instructions for a guy that runs
> > a WISP for him to look over before weekly backups ar
Hi,
Is there either a step, or a recipe for a step between
--dry-run and actually running?
In a particular instance, --dry-run isn't enough. I want
to actually attempt to read the entire file in, but then write
it out to nowhere. I'm trying to see if it generates any disk
errors t
> On Sat, 2008-05-31 at 14:35 -0400, Tuc at T-B-O-H.NET wrote:
> > Is there either a step, or a recipe for a step between
> > --dry-run and actually running?
> >=20
> > In a particular instance, --dry-run isn't enough. I want
> > to actually attemp
>
> On Sat, 2008-05-31 at 18:16 -0400, Tuc at T-B-O-H.NET wrote:
> > > That would be --only-write-batch.
> > =20
> > Hrm, so it does But creates a $FILE.sh filename. Any
> > way to prevent that part?
>
> No. If you don't want the $FILE.sh, ju
