> [email protected] 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. If it does this, how do you tell in a bash script that anything went wrong. (Ok, yeah, I could grep the file for Errno...) Having an error code is how I handle it currently, and it seems the right way to do it. Only a run without ANY exceptions should return zero, IMO. -Greg _______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
