There is a horrendously simple way to do this under UNIX. Let the watchdog process fork the daemon with a full-duplex pipe (or two half-duplex pipes). Let one get the read end and the other the write end. At the beginning of each program,
select the handles for reading/writing (appropriately) but don't send anything on the pipes. If your select ever returns values during the process (you could even use asynchronous
IO to skip threading- just DON'T POLL!!!), you know the other is down and an error has occcured somewhere. This way you have the watchdog watching the daemon and the daemon watching the watchdog. If the daemon fails, re
fork it and log the error. If watchdog fails, log the error and cleanly quit the daemon. Obviously, it becomes
extremely important to have a bug-free, non-
deprecated watchdog. Good luck!
AgentM Systems nor Nasca Enterprises nor
Bone::Easy nor Macperl is responsible for the
comments made by
AgentM. Remember, you can build any logical system with NOR.
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.