Re: version 2.2 --remove-older-than behavior changed

[Eric Zolf]

Hi,

On 17/02/2023 04:10, tbsky wrote:
> 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?

What is there to add to what is already in the man page?


The following return codes have not been fully implemented so test 
before you rely on them.
Also note that they can be combined, so that for example a return code 3 
might be returned if a warning was found, then an error.

0 - OK:: the action was completely successful
1 - ERROR:: something fatal happened, the whole action failed
2 - WARNING:: any kind of unexpected behavior without complete failure
4 - FILE ERROR:: the action failed on a single file (or more), but it 
wasn't the reason for a complete failure
8 - FILE WARNING:: the action stumbled on a single file (or more), or 
detected differences in a comparaison

TIP: any other error code can and should be reported as a bug.


KR, Eric