Kloogy solution:
use IPC::Open3;
use IO::Select;
$cmd="find /fst/home/ -name '*ooo*'";
$pid = open3(*CMD_IN, *CMD_OUT, *CMD_ERR, $cmd);
close(CMD_IN);
$SIG{CHLD} = sub {
print "REAPER: status $? on $pid\n" if waitpid($pid, 0) > 0
};
$selector = IO::Select->new();
$selector->add(*CMD_ERR, *CMD_OUT);
while (@ready = $selector->can_read) {
foreach $fh (@ready) {
$line = scalar <$fh>;
if (fileno($fh) == fileno(CMD_ERR)) {print "STDERR: ", $line}
else {print "STDOUT: ", $line}
($line) || $selector->remove($fh);
}
}
close(CMD_OUT);
close(CMD_ERR);
- Annoyance: upon completion there are STDOUT: STDERR: in front of the prompt (easy to clean out in the next step)
- Observation of strange behavior:
The messages only come out in the "right" order the first time the program is run in a shell. Subsequent calls mess up the order. Thus I have to exit and reenter the shell each time I debug. Weird.
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.