I don't know of any monitoring interface to cron. So probably the only possibilites are
1) Monitor the logfile where cron posts its execution infos, maybe parse it with something like Regexp::Log
2) if you have the power to change crontab entries, you might add a wrapper script to every line that records the execution statistics to a file. Trivially this could be just adding 'time' before every command so that the user gets an email for every execution. The emails then would have to be captured and analyzed, which is the tricky part (A real wrapper script would be simpler overall in most cases)
In reply to Re: Parsing and monitoring Crontabs
by jethro
in thread Parsing and monitoring Crontabs
by mcobbley
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |