This does work for Proc::Daemon. Anything you want to do that involves file descriptors should be setup after the Init, which avoids a lot of problems. For example, what if your process forks several times, and each child then runs Proc::Daemon::Init()? They will all inherit the same filehandle, which can be annoying for some modules (if I recall correctly the biggest problem with Log::Log4perl is likely to be log entries that overlap) and disastrous for others (DBI handles in particular are something you want to make sure that your child processes aren't trying to share).

We're not surrounded, we're in a target-rich environment!

In reply to Re^2: Proc::Daemon and Log::Log4perl by jasonk
in thread Proc::Daemon and Log::Log4perl by Excalibor

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.