Ok.. well, first off you'll need to save some (persistent) state. You could do this in files, variables in the parent process, environment variables, whatever.
The first thing that comes to mind is to start off just making a folder for the info, and have each child create a log file named after it's pid, with it's arguments, a log of recent restarts (say, the last 5 min,).
I'd also have each process touch it's pid file every 10 seconds or so, so the parent which is polling the data can know that a pid file not touched in the last 30 seconds needs to have it's child killed and restarted a minute or so later.
Once you have the logic in for restarted dead/stopped children, it's just a matter of adding conditionals and changing the sleep time for the 5 minute stop. Similarly the custom processes will just take an additional conditional checking on the restart history.
Hope that helps,
- D
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.