summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbescoto <bescoto@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2005-12-30 18:33:46 +0000
committerbescoto <bescoto@2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109>2005-12-30 18:33:46 +0000
commitca1b97bbb42668e10a96a57fbe7c96df934ac84f (patch)
tree7b94f6d2c6a4af773ba43f8d73a735827e8e219c
parentbe04183e6012d842448a7363f1202f5a1e093d6c (diff)
downloadrdiff-backup-ca1b97bbb42668e10a96a57fbe7c96df934ac84f.tar.gz
Clarify exit status
git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/branches/r1-0@733 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109
-rw-r--r--rdiff-backup/rdiff-backup.16
1 files changed, 3 insertions, 3 deletions
diff --git a/rdiff-backup/rdiff-backup.1 b/rdiff-backup/rdiff-backup.1
index dc69c1b..0f3070d 100644
--- a/rdiff-backup/rdiff-backup.1
+++ b/rdiff-backup/rdiff-backup.1
@@ -923,9 +923,9 @@ rdiff-backup is run with high verbosity.
.SH EXIT STATUS
If rdiff-backup finishes successfully, the exit status will be 0. If
-there is an error, it will be non-zero (usually 1, but don't depend on
-this specific value). When setting up rdiff-backup to run
-automatically (as from
+there is an unrecoverable (critical) error, it will be non-zero
+(usually 1, but don't depend on this specific value). When setting up
+rdiff-backup to run automatically (as from
.BR cron (8)
or similar) it is probably a good idea to check the exit code.