As Joost points out, system is the correct way to do this, but there is one caveat. Apparently--see 271092--it's not guaranteed that STDOUT is reopened on file descriptor 1 and STDERR on file descriptor 2. Thus it would be safer to code this way:
open (STDOUT, ">$log_dir/$process.log") or die "cannot open log: $!\n"
+;
if (fileno(STDOUT) != 1) {
  use POSIX;
  POSIX::dup2(fileno(STDOUT), 1) or die "dup2: $!\n";
}
open (STDERR, ">&STDOUT") or exit 2;
flock(STDOUT, LOCK_EX | LOCK_NB) or exit 3;

[download]

In reply to Re: Problem dup'ing STDOUT by Thelonius
in thread Problem dup'ing STDOUT by nimdokk

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.