Step between --dry-run and running?
Tuc at T-B-O-H.NET
ml at t-b-o-h.net
Sat May 31 22:16:49 GMT 2008
> 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?
> > 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 that may hurt during an actual transfer.
> That would be --only-write-batch.
Hrm, so it does.... But creates a $FILE.sh filename. Any
way to prevent that part? Also, should running it twice in a row
quickly produce 2 files that should diff the same, or is something
stored in there that would prevent a diff from being the same?
More information about the rsync