Re: pseudo tty stderr capture problem.

From: Andrew Gabriel (andrew_at_cucumber.demon.co.uk)
Date: 07/17/03 

Date: 17 Jul 2003 10:05:25 GMT

In article <23c4da62.0307151507.7fbba54c@posting.google.com>,
        minshei@hotmail.com (Min Shei) writes:
> Hi, All,
>
> I was trying to make a simple pseudo tty program to capture the stdout
> and stderr from the child process to avoid the stdout buffering
> problem. The following is a little program I found on one new group
> here (written by Richard Tobin, 1990). However, this program captures
> the child's stdout very well. But I just couldn't make it work for the
> stderr of the child process. My platform is Solaris 2.7.
>
> Has anyone here had the same problem? The program could be compiled
> by:
> cc -o nobuf nobuf.c pseudopipe.c

Didn't come close to compiling for me. 

-- 
Andrew Gabriel
Consultant Software Engineer

Relevant Pages

  • [ANN] open4-0.9.4
    ... open child process with handles on pid, stdin, stdout, and stderr: ... require "open4" ...
    (comp.lang.ruby)
  • Re: does IO.read block?
    ... Assume an application as a child process that frequently writes to stdout and stderr. ... The parent process at the other end of those two pipes only reads the stdout pipe. ...
    (comp.lang.ruby)
  • Re: Problem excuteing RPM form java
    ... When your rpm has a pre or postinstallation script there is probably ... you read from stdout until EOF is reached ... so you don't even begin to read from stderr until after ... while you are still reading stdout, so the child process blocks. ...
    (comp.lang.java.help)
  • [ANN] open4-0.5.1
    ... open child process with handles on pid, stdin, stdout, and stderr: ... require "open4" ...
    (comp.lang.ruby)
  • [ANN] open4-0.9.0
    ... open child process with handles on pid, stdin, stdout, and stderr: ... require "open4" ...
    (comp.lang.ruby)