# run a subprocess which output to STDOUT 
`pgp -h`;

[download]
Hmm. That's a confusing statement. You've got a void use of backticks (minus 2 for style points), and that's capturing the stdout of the pgp command, then discarding it. So, it's not going to STDOUT at all.

Perhaps what you mean is that the child process stderr is going to Perl's STDERR, which you've aliased (not dup'ed) to STDOUT. If so, that's not what I would have gotten from the comments. {grin}

The normally accepted dup'ing of STDOUT to STDERR that doesn't raise the uglies of not working with child processes and symbol table glob mangling is: 

open STDERR, ">&STDOUT";

[download]

-- Randal L. Schwartz, Perl hacker

In reply to RE: Intermixing STDOUT and STDERR to a file by merlyn
in thread Intermixing STDOUT and STDERR to a file by princepawn

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.