Fix issue with redirection in run/port (and, by extension, run/string)

We would initially create a pipe, dup(2) that onto fd 1 in the forked
process and open an output port on the original fd.  This resulted in
a pretty nasty bug: if the fd would be redirected (by number) later,
it would not affect the output port because that was set up to point
to the original fd.

Instead, open an output port to the newly set up stdout and close the
direct pipe port.

0 files changed, 0 insertions, 0 deletions