, it means
something didn’t go as expected—perhaps it's your super critical database
failed to back up. In such cases, surfacing the issue rather than silently
ignoring it aligns with the tool's purpose.
The current implementation, however, supports both use cases. If your want
to igno
ck up. In such cases, surfacing the issue rather than silently
ignoring it aligns with the tool's purpose.
The current implementation, however, supports both use cases. If your want
to ignore return code 2, you can easily work around this by creating a
simple Bash function, such as:
rdiff-
Hello,
I've finally gotten around to an updated version of rdiff-backup where
the return codes are all weird.
I have read through the thread:
https://lists.nongnu.org/archive/html/rdiff-backup-users/2023-02/msg00034.html
I have to concur that it's very wrong for the rdiff-backup to succeed
