STDOUT and STDERR redirection fails for forked process

[Peter]

Hi,

I am trying to redirect STDERR to STDOUT and catching the returncode
using the script below.
Currently every error is redirected to the terminal instead of to
STDERR or STDOUT, so i am not able to catch the output if it
originates from a process's STDERR.

Any ideas/suggestions why STDERR is not redirectoed ? (i assume that
the RC is always 0 because of the failed STDERR redirection).

## Issue the command by forking the process and monitoring the
output
if (open STATUS, "$cmdstr 2>&1 |") {
while (<STATUS>) {
$result .= $_ ;
}
close STATUS ;
$rcverror = $? >> 8;
$errmsg = $! ;

}
else {
$errmsg = "Fork failed for \'$cmdstr\'" ;
$rcverror = -2 ;
}

# reset the alarm
alarm(0) ;
$rcvtimeout = 0 ;
} ;

Peter

 

[Brian McCauley]

Hi,

I am trying to redirect STDERR to STDOUT and catching the returncode
using the script below.
Currently every error is redirected to the terminal instead of to
STDERR or STDOUT, so i am not able to catch the output if it
originates from a process's STDERR.

Any ideas/suggestions why STDERR is not redirectoed ? (i assume that
the RC is always 0 because of the failed STDERR redirection).

## Issue the command by forking the process and monitoring the
output
if (open STATUS, "$cmdstr 2>&1 |") {
while (<STATUS>) {
$result .= $_ ;
}
close STATUS ;
$rcverror = $? >> 8;
$errmsg = $! ;

}
else {
$errmsg = "Fork failed for \'$cmdstr\'" ;
$rcverror = -2 ;
}

# reset the alarm
alarm(0) ;
$rcvtimeout = 0 ;
} ;

Peter

I can't see anything wrong with that code, but then again I can't run
it because it's incomplete and the problem could easily lie in the
bits you don't show us anyhow.

Please post a _minimal_ but _complete_ script that you've actually run
and found to produce the effect you are trying to understand.

This advice, and much more, can be found in the posting guidelines.