>> ... and gather stdout, stderr.
Quoting from perlop ...
qx/STRING/
...
To capture a command's STDERR and STDOUT together:
$output = `cmd 2>&1`;
This works for me, on WinXP, as in the example below.
To generate output going to stdout in one case and to stderr in another case, my script calls a Perforce command (p4 change -o) with a good changelist (43026) - this writes to stdout, and then with an inexistent one (143026) - this writes to stderr.
#!/usr/bin/perl
use strict;
use warnings;
printf STDERR "1 stdout: %s\n\n", ` p4 change -o 43026 `;
printf STDERR "2 stdout: %s\n\n", ` p4 change -o 143026 `;
printf STDERR "3 stdout+stderr 2>&1: %s\n\n", ` p4 change -o 143026
+2>&1 `;
__END__
# typical output on my machine #
1 stdout: # A Perforce Change Specification.
Change 143026 unknown.
2 stdout:
3 stdout+stderr 2>&1: Change 143026 unknown.
HTH
rudif
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.