I played with Thread::Pool, and seems fine. What I did is:
  1. fork a new process
  2. exit the main process
  3. in the forked process, initialize Thread::Pool
  4. the forked process start an endless loop to dispatch jobs to thread pool. The job my threads do is simple, just take two numbers, and return the sum.
Two points:
  1. It sounds to me more logical to fork first, and then initialize the Thread::Pool, indeed the Thread::Pool object has nothing to do with the main process, from the design view, it should be contained in a smaller as possible scope.
  2. The error msg you got saying exit when other threads running, is because you exited main process, without first stop or join all threads.

In reply to Re: daemonizing and threads by pg
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.