From "perldoc IPC::Open3" (the second paragraph):

If WTRFH begins with `<&', then WTRFH will be closed in the parent, and the child will read from it directly. If RDRFH or ERRFH begins with `>&', then the child will send output directly to that filehandle. In both cases, there will be a dup(2) instead of a pipe(2) made.

So you should be able to do what you want simply by change one line to: my $pid = open3("<&STDIN", ">&OUTPUT", ">&ERRLOG", $cmd) or die "$!"; Note that this will close those file handles in the parent as can be seen by this test program which does put the desired output into the specified files:

#!/usr/local/bin/perl

# Script to test IPC::Open3
# Runs, displays $pid to STDOUT, but opened
# files are empty.

use strict;
use warnings;

if( @ARGV ) {
    print STDOUT "StdOut!\n";
    print STDERR "StdErr!\n";
    exit( 0 );
}

#use diagnostics;
use IPC::Open3;

$|++;

my @cmd = ($^X,$0,"Test");

open(ERRLOG, ">error.log") or die "Can't open error log! $!";
open(OUTPUT, ">output.log") or die "Can't open output log! $!";

my $pid = open3("<&STDIN", ">&OUTPUT", ">&ERRLOG", @cmd) or die "$!";

print "PID was $pid\n";

close(ERRLOG) or die "Can't close filehandle! $!";
close(OUTPUT) or die "Can't close filehandle! $!";
defined( my $x= <STDIN> ) or warn "Can't read STDIN: $!\n";
[download]

and then says:

PID was 416
readline() on closed filehandle main::STDIN at open3.pl line 32.
Can't read STDIN: Bad file descriptor
[download]

So you might want to dup STDIN first: open( IN, "<&STDIN" ) or die "...: $!\n"; and pass in "<&IN" instead of "<&STDIN".

        - tye (but my friends call me "Tye")

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.