Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document use of Cronic or alternatives #10

Open
tgharold opened this issue Jul 23, 2015 · 1 comment
Open

Document use of Cronic or alternatives #10

tgharold opened this issue Jul 23, 2015 · 1 comment
Milestone

Comments

@tgharold
Copy link
Owner

It's probably more important to capture error output so that the error messages can be emailed to a system administrator. The "cron" system already sends an email to the owner of the cron job with the regular output from the script.

Will need to create a temporary file and fill it with error messages and other informational information as the script runs, so that it can be emailed during clean-up after a fatal error occurs.

@tgharold
Copy link
Owner Author

tgharold commented Aug 5, 2015

This should be handled instead by something like Cronic, Shush, or Cronwrap. I need to add that to the the README or INSTALL

Cronic: http://habilis.net/cronic/
Shush: http://web.taranis.org/shush/
Cronwrap: http://www.uow.edu.au/~sah/cronwrap.html

@tgharold tgharold changed the title Capture error output to be mailed to sysadmin Capture error output to be mailed to sysadmin (document use of Cronic) Aug 5, 2015
@tgharold tgharold changed the title Capture error output to be mailed to sysadmin (document use of Cronic) Error output to be mailed to sysadmin (document use of Cronic) Aug 5, 2015
@tgharold tgharold changed the title Error output to be mailed to sysadmin (document use of Cronic) Document use of Cronic or alternatives Aug 11, 2015
@tgharold tgharold added this to the Current milestone Aug 11, 2015
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

No branches or pull requests

1 participant