Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site l5.uucp
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!ucbvax!ucdavis!lll-crg!l5!gnu
From: gnu@l5.uucp (John Gilmore)
Newsgroups: net.unix
Subject: Re:  tee command without buffering
Message-ID: <331@l5.uucp>
Date: Wed, 11-Dec-85 08:00:10 EST
Article-I.D.: l5.331
Posted: Wed Dec 11 08:00:10 1985
Date-Received: Fri, 13-Dec-85 08:07:55 EST
References: <509@brl-tgr.ARPA>
Organization: Nebula Consultants in San Francisco
Lines: 13

In article <509@brl-tgr.ARPA>, kvancamp@ardc.arpa (LCWSL) writes:
> Thanks to all of you who responded to my question about stopping buffering
> of the tee command (so I could see my output at the same time I echo it
> to a file)...what I wanted is
> impossible because the buffering is inherent in the system (i.e., it isn't
> the fault of tee...

The problem is that a program whose output is a pipe will buffer
up a large block of stuff before it writes it to the pipe.  If the output
is to a terminal, it sends it out as soon as the program writes it.
This is done by the standard I/O library to improve performance.
Thus if you have xxx | tee file  the problem is in stdio in xxx; it's
not in "tee".  There's no particularly good solution.