Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Date:	Mon, 13 Mar 2000 14:40:52 +0200
From:	Paul Sokolovsky <paul-ml AT is DOT lg DOT ua>
X-Mailer:	The Bat! (v1.32) S/N AB51B607
Reply-To:	Paul Sokolovsky <paul-ml AT is DOT lg DOT ua>
X-Priority:	3 (Normal)
Message-ID:	<3611.000313@is.lg.ua>
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Cygwin piping misbehaviour
Mime-Version:	1.0

Hello cygwin,

  While porting textutils with my tools, I found that running (under
sh) cat <file>|head with sufficiently large file makes cat complain
about broken pipe (I haven't yet implemented SIGPIPE generation). I
tried that on cygwin and got no error. So, I considered behaviour of
my version queer. But looking at source code of both cat and head,
reading susv2 more and more assured me that I'm doing fine. I finally
relieved when run that on linux and got "Broken pipe" report from
shell.

      Now question: why cygwin passes that silently? To my
understanding, that sh who doesn't report termination by SIGPIPE. I
have the same with both bash and ash. B20.1 on 95 and NT.

--
Paul Sokolovsky, IT Specialist
http://www.brainbench.com/transcript.jsp?pid=11135



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -