A more general solution might be to write an event logging module and 'use' it in all your scripts. Then any time something 'happens' you can invoke an API in that event-logging module and log it to a file (or better yet, a relational database). Hey, presto, you've got a decent historical picture of what has been happening. You can write the CGI script that presents the 'current picture' once and make it configurable/filterable for various slices of the event log.
Or you could stick with your cron log-sweeping idea, especially if you have a lot of shell scripts. The above is just an idea that popped into my head, and may not be well-thought-out. Take it or leave it. :)
No good deed goes unpunished. -- (attributed to) Oscar Wilde
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.