I ++ed your node, but please note that on some systems you'd have to fork() and exit() twice to completely dissociate from the original process's resources. fork(), exit(), and POSIX::setsid() is even better.

Proc::Daemon has its good points, but why would I want it to reopen three file handles if I'm going to turn around and close them anyway? That doesn't seem like a very useful thing to do in the generic case. Still, for production code it wouldn't hurt to use it just for the fact that someone else has already debugged it.

Christopher E. Stith
use coffee;

In reply to Re: Re: Daemon possessed perl by mr_mischief
in thread Daemon possessed perl by outcast

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.