Re: [rdiff-backup-users] rdiff-backup completes without errors, but then have a corrupt archive...

[Matthew Flaschen]

address@hidden wrote:
> I'm not sure if no 3 covers file errors like files being busy etc...
> I'd guess that even if it did, I'd like a code that is "basically
> everything went smoothly, but some files were locked, or otherwise
> unavailable."
> 
> This will tell us we got a "good" backup, but that it has some
> missing files.

I would not consider that a overall failure (with a non-zero exit code).
 It should print the error text to stderr (which I think it already does
even on default verbosity), but still return 0 in such cases.

Matt Flaschen