While Filter::Handle looks like the right module for the job, I'd probably just do it by hand as below. If your error output isn't going to be line-based, you should use select to poll for input within the child. Season to taste. 
my $err_file = "error.log";
open(ERRLOG, "+>>logs/system/$err_file") or die "Could not open logfil
+e:$!\n";
flock(ERRLOG,2);

# Was *STDERR = *ERRLOG;
my $child = open(STDERR, '|-');
if ($child < 0) { die "Could not fork: $!\n" }
if ($child == 0) {
    while (<>) {
        printf ERRLOG '%s %s', scalar(localtime), $_;
    }
    exit 0;
}
print "One\n";
print STDERR "Foo\n";
print "Two\n";
print STDERR "Bar\n";

# and ends with:

flock(ERRLOG,8);
close(ERRLOG);

[download]
The PerlMonk tr/// Advocate

In reply to Re: Formatting STDERR by Roy Johnson
in thread Formatting STDERR by DaWolf

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.