|The stupid question is the question not asked|
Re: Parsing and monitoring Crontabsby JSchmitz (Canon)
|on Jul 12, 2010 at 15:03 UTC||Need Help??|
First of all welcome to Perl!
I have to say that I agree with JavaFan seems like you are re-inventing the wheel here not only can you look at the logs you can have status emailed to you
cmd | mail -s "Subject of mail" user
If you wish to mail the output to someone not located on the machine, in the above example, substitute user for the email address of the person who wishes to receive the output.
If you have a command that is run often, and you don't want to be emailed the output every time, you can redirect the output to a log file (or /dev/null, if you really don't want the output). e,g
cmd >> log.file
Notice we're using two > signs so that the output appends the log file and doesn't clobber previous output. The above example only redirects the standard output, not the standard error, if you want all output stored in the log file, this should do the trick:
cmd >> logfile 2>&1
You can then set up a cron job that mails you the contents of the file at specified time intervals, using the cmd:
mail -s "logfile for cmd" <log.file
Have fun!! oh and s/PERL/Perl