Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!pacbell!rtech!rain!jas
From: jas@rain.rtech.UUCP (Jim Shankland)
Newsgroups: comp.unix.wizards
Subject: Re: Stdio buffering question
Message-ID: <2163@rtech.UUCP>
Date: 13 Jun 88 17:39:13 GMT
References: <16124@brl-adm.ARPA> <4999@super.upenn.edu>
Sender: news@rtech.UUCP
Reply-To: jas@rtech.UUCP (Jim Shankland)
Distribution: na
Organization: Eddie Enterprises
Lines: 16

In article <4999@super.upenn.edu> david@linc.cis.upenn.edu.UUCP (David Feldman) writes:
>When piping, stderr gets buffered so that it may be separated from stdout.
>Stdout goes through the pipe, and when it is closed, the stderr buffer gets
>flushed through the pipe. That is assuming you have redirected stderr through
>the pipe also.   This is a documented feature, and I believe it is a csh thing.
>I can't remember off hand.  I don't think fflush() will help, especially
>if it is done in csh.  One way csh could implement this feature is to
>attach stderr to a file and then throw the file down the pipe when stdout
>closes.  Any csh hackers know the details on this thing?  I am guessin'.

I'll say.

Jim Shankland
  ..!ihnp4!cpsc6a!\
               sun!rtech!jas
 ..!ucbvax!mtxinu!/
"The road to hell ... is where the heart is"