ccollect/doc
jll2 544a7d269e Create rsync_failure_codes option.
User may optionally create a file rsync_failure_codes with a
newline-separated list of rsync return codes that are to be
regarded as complete failure.

If rsync exits with such a code, then the backup will be marked
for deletion during the next ccollect run (if delete_incomplete).

I added documentation for this feature in doc/ccollect.text

In my experience (yours may differ), two rsync exit codes that
belong in this file are 12 and 255.  I have seen 12 result from
ssh errors and 255 result from a kernel module conflict.  In both
cases, the resulting backups were empty.  Without the
rsync_failure_codes option, such errors cause good backups to be
deleted, as per c_interval, leaving behind the new empty backups.

In the long run, we may want a different and more comprehensive
method for analyzing rsync errors.  In the short run, I find this
option necessary.
2009-06-24 17:01:14 -07:00
..
braindumps add braindumps 2008-03-14 17:54:29 +01:00
changes add changes for the next release 2009-06-10 09:56:13 +02:00
man minor notice changes 2008-03-17 11:42:06 +01:00
todo update todo and changes 2009-02-02 12:16:04 +01:00
ccollect-DE.text really mark the german documentation as outdated 2008-03-17 08:30:07 +01:00
ccollect-restoring.text +nc 2008-08-19 15:25:46 +02:00
ccollect.text Create rsync_failure_codes option. 2009-06-24 17:01:14 -07:00
gpl3-header remove cinit fragments 2008-03-07 23:01:27 +01:00
HACKING [DOC] give some hints on how to hack ccollect 2009-06-20 21:00:21 +02:00
logwrapper.text More doc on logwrapper 2007-06-22 11:08:48 +02:00
release-checklist plus date 2006-10-20 00:05:10 +02:00