From 7661c430367e74c4d20e886fbf699365d949752f Mon Sep 17 00:00:00 2001 From: bescoto Date: Tue, 9 Sep 2003 18:00:04 +0000 Subject: Added section on exit status, TODO --datadir note git-svn-id: http://svn.savannah.nongnu.org/svn/rdiff-backup/trunk@420 2b77aa54-bcbc-44c9-a7ec-4f6cf2b41109 --- rdiff-backup/TODO | 4 +++- rdiff-backup/rdiff-backup.1 | 9 +++++++++ 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/rdiff-backup/TODO b/rdiff-backup/TODO index 960bd44..50204ca 100644 --- a/rdiff-backup/TODO +++ b/rdiff-backup/TODO @@ -1,3 +1,5 @@ +Look at manual page examples. + Consider adding --datadir option (Jean-Sébastien GOETSCHY) See if regressing takes too much memory (large directories). @@ -8,7 +10,7 @@ Use ctime to check whether files have been changed. See message: http://mail.gnu.org/archive/html/rdiff-backup-users/2003-06/msg00050.html by Andrew Bressen. -Profile 0.13.0 +Profile 0.13.x Look at EAs when unames change. diff --git a/rdiff-backup/rdiff-backup.1 b/rdiff-backup/rdiff-backup.1 index f3db272..a057988 100644 --- a/rdiff-backup/rdiff-backup.1 +++ b/rdiff-backup/rdiff-backup.1 @@ -861,6 +861,15 @@ option. The log file is not compressed and can become quite large if 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 +.BR cron (8) +or similar) it is probably a good idea to check the exit code. + .SH BUGS rdiff-backup uses the shell command .BR mknod (1) -- cgit v1.2.1