Re: Exit status when there are no files to remove

Hi,=20

First, Return Code 2 isn't an error (that would be 1), it's a warning, so =
you can very well ignore it if you decide so=2E This is what differentiated=
 return codes are meant for after all=2E The codes are documented in the ma=
n page=2E
Second, there is an RFE for this <https://github=2Ecom/rdiff-backup/rdiff-=
backup/issues/1078> so you can hook up to it=2E=20

Hope this helps, Eric

On 29 August 2025 19:28:15 CEST, Stephen Isard <q83zi5r02@sneakemail=2Ecom=
> wrote:
>Hello,
>
>I have a script which performs a backup and then tries to remove all incr=
ements older than 180 days=2E  Sometimes, depending on when the script has =
run, there aren't any increments older than 180 days=2E  rdiff-backup then =
returns with an exit code of 2, which causes the cron job that launched the=
 script to send me an email about it, which I don't want=2E Is there a way =
to stop rdiff-backup from considering the case where no increments are olde=
r than 180 days as an error?  I thought that --force might do it, but no=2E
>
>Thanks,
>
>Stephen Isard
>