Several possibilities:
  1. Don't worry about it. Let the user handle this, using standard Unix redirection. This is the easiest possibility for you, and probably the most flexible for users.
  2. Ignore STDERR for now (if run from cron, that output will be mailed to the job owner), and use two-arg select to change the default output filehandle.
  3. Re-open STDOUT and STDERR elsewhere: 
    open(STDOUT, '>daemon.log') or die "Can't open daemon.log: $!";
open(STDERR, '>daemon.err') or die "Can't open daemon.err: $!";

    [download]
  4. Skip the forking altogether. This may not be an option, but I don't see what it adds to the process, unless you're trying to get init as your parent. Then it makes sense. :)

In reply to Re: Messin around with fork() and fd's by chromatic
in thread Messin around with fork() and fd's by snafu

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.