Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: tee piping to head gives error message
Date:	Mon, 7 Feb 2005 18:31:47 -0000
MIME-Version:	1.0
In-Reply-To:	<NUTMEGWEsBk31TZ14eB000006d3@NUTMEG.CAM.ARTIMI.COM>
Message-ID:	<NUTMEGBZTW5k1Ed28kI000006d7@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	07 Feb 2005 18:31:47.0202 (UTC) FILETIME=[48027E20:01C50D43]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Dave Korn
> Sent: 07 February 2005 18:13


> 
> > But the number of lines/bytes at which the error disappears 
> > does not seem to be constant.


  Ah, I just managed to reproduce this.  That is indeed rather strange.  Hmm.  

  Oh, hang on, it gets more interesting, I just got it to *really* fail.  Here's
a test on a file with 4207 lines in it.....

dk AT mace /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 > /dev/nu
ll
tee: write error
dk AT mace /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 > /dev/nu
ll
dk AT mace /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 > /dev/nu
ll
dk AT mace /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 > /dev/nu
ll
tee: write error
dk AT mace /artimi/firmware>
dk AT mace /artimi/firmware>
dk AT mace /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 > /dev/nu
ll
tee: write error
dk AT mace /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 > /dev/nu
ll
tee: write error
dk AT mace /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 > /dev/nu
ll
Terminate batch job (Y/N)?


  Wow.  The last time where I tried it, it paused for a long time as if it had
hung, and then managed to kill my entire bash shell and cygwin.bat session.  I
guess there really is a bug there.

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -