Whoops, I wrote in my previous message:
> So you lose the copy, but rsync still exits with a non-zero code,
> which makes it look like there was nothing to transfer (e.g., no
> change to the file).
That should have said "exits with a zero exit code" - e.g., it exits
looking like it was successfu
Bennett Todd [[EMAIL PROTECTED]] writes:
> 2000-12-22-16:11:08 Richard Odom:
> > Is there anything like a completion code that can be captured to use for
> > a check/restart?
>
> Well, I'm pretty sure rsync exits with nonzero status if it bombs
> off, but I can't say I've had it bomb off enough
2000-12-22-16:11:08 Richard Odom:
> If a new file is being sent and communication is lost..Is the partial
> file retained and then only the 'changed' information is sent on the
> next transfer? Or is the partial file lost?
Either way, that's controlled by the "--partial" option. If you must
keep
If a new file is being sent and communication is lost..Is the partial
file retained and then only the 'changed' information is sent on the
next transfer? Or is the partial file lost?
Is there anything like a completion code that can be captured to use for
a check/restart?
We often have bad or in