|
| From: | tbsky |
| Subject: | Re: version 2.2 --remove-older-than behavior changed |
| Date: | Fri, 17 Feb 2023 11:10:34 +0800 |
| User-agent: | Roundcube Webmail/1.3.16 |
qx6uwumzvv@liamekaens.com 2023-02-17 03:41:
IMHO, "No increment is older than ...." is normal behavior and should not cause a warning, especially since nonzero status codes are considered abnormal termination by most shells (even the Python docs <https://docs.python.org/3/library/sys.html#sys.exit> mention this), and can cause backup scripts to terminate.
yes that's the behavior of version 2.0.5. with rdiff-backup 2.2 I see man page mention:
RETURN CODES
2 - WARNING
any kind of unexpected behavior without complete failure
but I don't know what condition meet the description. when
rdiff-backup is working there are many things will happen like:
"file can not open", "fifo files too long", "xattr can not backup". will
these become "return code 2" in the future? currently they are still
"return code 0".
should I say "return code 2" means the job is still finished but with
some kind of warnings?
| [Prev in Thread] | Current Thread | [Next in Thread] |