One heavyweight alternative, almost not worth mentioning, is to have a grandparent process fork off the parent and just sit around and log all of the parent's STDERR output.

If you find a way of not patching this on a case-by-case basis, I'd be interested. I tend to go the other direction and log output from warn/die/croak/etc and the error codes I get back, since I find there is a lot of marginal stuff, outside of my control, that goes to stderr. If something turns up that I need to monitor from stderr, then I resort to trapping it on a case-by-case basis (i.e. by sending it to a temp file, forking a child and reading the stderr output from it, etc).

In reply to Re: Catching fork() with tied STDERR by bluto
in thread Catching fork() with tied STDERR by hv

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.