Thanks, I was making the process of maintaining the actual time slept versus how much time had elapsed during a particular iteration of the loop entirely too complicated. The simple loop does ensure the daemon sleeps for the correct amount of time.

However, this does leave defunct processes sitting in the process table until the daemon interates again and I reap the processes. Which I can live with, but ideally I'd like to know if it is possible to avoid.

Is there a way to create a thread to handle the signals immediately and store the exit statuses in a shared hash? I don't know if I should be mixing ithreads and forking to begin with, but that would be the perfect solution to my problems.

Thanks again,
overbyte

In reply to Re^2: SIGCHLD and sleep() by overbyte
in thread SIGCHLD and sleep() by overbyte

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.