comment on

The question is, however, how to use open3 in this case. You could supply different handles for the child's STDOUT and STDERR, but then it becomes very hard to communicate with the child. (You'd need to use IO::Select to avoid deadlocks.)

If you don't mind combining the child's STDOUT and STDERR into one stream, that's a much simpler option.

$pid = open3(
   my $to_child,   # Autovivified when false.
   my $fr_child,   # Autovivified when false.
   undef,          # Same as $fr_child when false.
   $somecommand,
   @args
);

...

waitpid($pid, 0);
[download]

In reply to Re: Pipe, STDERR, STDOUT, and friends by ikegami
in thread Pipe, STDERR, STDOUT, and friends by devnul

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks