Pushing some sort of confirmation out to a single master would be the easiest thing to do (using ssh passwordless auth), but this would actually be neat situation to implement some sort of distributed confirmation algorithm that doesn't have a single point of failure - that being the connection between your master and any of the servers you'd like to keep tabs on.

If you have some time to think about the solution and a lot more time to code it, POE might be the answer, but in reality a simple master daemon listener solution would not take long to craft from the many Perl daemon examples out there.

You could use a simple scheme where there is the master listener waiting for "DONE_SUCCESS" from all respective servers. On hearing "DONE_SUCCESS", the master daemon would send an ACK back to the server in question (requires a listener on that end, too). The server trying to check in would continue to send "DONE_SUCCESS" messages until it finally hears the "ACK" from the master.

If you're interested in a solution like that, let me know and I'll go over it in more detail.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.