You can split the fork and the exec up if open mashes them together too much.
pipe CHILDREAD, CHILWRITE;
defined( my $pid = fork ) or die "fork: $!";
if ( $pid ) {
# read on CHILDREAD;
} else {
open STDERR, ">&CHILDWRITE";
open STDOUT, ">&CHILDWRITE";
exec( $somecmd );
}
This is precisely the type of plumbing that a shell will do when you say 2>&1, except without the unportable syntax ;-)
That said, IPC::Run and friends already abstract all of this out, so there's no need to reinvent the wheel.
-
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.
|