The line exit 0 if $child; indeed exits the parent after fork. That is normal for daemon spawning. Is the problem intermittent, perhaps half the time? It may be that the parent sometimes exits too quickly, causing SIGHUP to be sent to the child before it establishes its independence. Setting $SIG{HUP} to IGNORE or an empty handler before fork should fix that.

Customarily, a daemon's SIGHUP handler causes it to reread configuration files and reconfigure accordingly. That can be set up after the daemon is well started.

You probably should get your daemonizing out of the way before threading. Have you considered daemonizing in a BEGIN block, before use threads; is even seen?

After Compline,
Zaxo

In reply to Re: daemonizing and threads by Zaxo
in thread daemonizing and threads by Anonymous Monk

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.