You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
r2e should return a non-zero exit when something wrong happens.
Currently, this only seems to be the case when it cannot parse its command line arguments.
For other kinds of failures already logged as "errors", the program still seems to exit with status code 0.
Because of this, failures go undetected when running the program through a cron job or systemd timer:
Dec 04 11:49:46 h systemd[1]: Starting rss2email-notifier.service...
Dec 04 11:49:49 h r2e[16099]: 2020-12-04 11:49:49,357 [ERROR]
Dec 04 11:49:49 h r2e[16099]: 2020-12-04 11:49:49,357 [ERROR] cause: sendmail exited with code 69
[...]
Dec 04 11:50:19 h r2e[16099]: 2020-12-04 11:50:19,126 [ERROR]
Dec 04 11:50:19 h r2e[16099]: 2020-12-04 11:50:19,126 [ERROR] cause: sendmail exited with code 69
Dec 04 11:50:19 h systemd[1]: rss2email-notifier.service: Succeeded.
Dec 04 11:50:19 h systemd[1]: Finished rss2email-notifier.service.
The text was updated successfully, but these errors were encountered:
r2e
should return a non-zero exit when something wrong happens.Currently, this only seems to be the case when it cannot parse its command line arguments.
For other kinds of failures already logged as "errors", the program still seems to exit with status code 0.
Because of this, failures go undetected when running the program through a cron job or systemd timer:
The text was updated successfully, but these errors were encountered: