Hi, 

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. This is what differentiated return 
codes are meant for after all. The codes are documented in the man page.
Second, there is an RFE for this 
<https://github.com/rdiff-backup/rdiff-backup/issues/1078> so you can hook up 
to it. 

Hope this helps, Eric

On 29 August 2025 19:28:15 CEST, Stephen Isard <[email protected]> wrote:
>Hello,
>
>I have a script which performs a backup and then tries to remove all 
>increments older than 180 days.  Sometimes, depending on when the script has 
>run, there aren't any increments older than 180 days.  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. Is there a way to 
>stop rdiff-backup from considering the case where no increments are older than 
>180 days as an error?  I thought that --force might do it, but no.
>
>Thanks,
>
>Stephen Isard
>

Reply via email to