________________________________

From: Tillmann Basien


 >   I spawn a command which send to stdout and stderr. But I only can
expect on the stdout strings.
 >   How can I also expect on the stderr strings?

 
How urgent is it that you keep stdout and stderr separate? My first
thought - what I call the "cheating solution" is to call
a script that starts your command. Within that script, you would start
your command as:
 
#! /bin/ksh
 
  mycommand 2> &1
 
(or use the syntax of whatever the batch/shell command language you have
available). This says "start mycommand, and write its stderr out to the
same file descriptor as its stdout".
 
 
 -- 

<URL: http://wiki.tcl.tk/ > 

Even if explicitly stated to the contrary, nothing in this posting

should be construed as representing my employer's opinions.

<URL: mailto:lvirden@[...].com >  <URL: http://www.purl.org/NET/lvirden/
>