Skip to content

Conversation

kevinoconnor7
Copy link

Currently any errors coming the underlying tarsnap commands are logged. This is not threaded back to the entrypoint of the application though, so we end up exiting with a zero code despite one or more of the jobs having failed. This makes monitoring the status of tarsnapper impossible. One would have to know to regularly check its logs to ensure it's actually backing things up.

Fixes #39

Currently any errors coming the underlying tarsnap commands are logged. This is
not threaded back to the entrypoint of the application though, so we end up
exiting with a zero code despite one or more of the jobs having failed. This
makes monitoring the status of tarsnapper impossible. One would have to know to
regularly check its logs to ensure it's actually backing things up.

Fixes miracle2k#39
@jeffwidman
Copy link
Contributor

Ooh, I didn't even realize it always returned 0, would be great to see this merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

set error exit status when backup not done

2 participants