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 20:59:20 +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: <12874.000313@is.lg.ua>
To: Chris Faylor <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re[2]: Cygwin piping misbehaviour
In-reply-To: <20000313110127.F1005@cygnus.com>
References: <20000313110127 DOT F1005 AT cygnus DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello Chris,

Chris Faylor <cgf AT cygnus DOT com> wrote:

[]

>>      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.

CF> You're a programmer, right?  And you have source code available...

    Nice answer. Yes, I can dig source, find cause, and even submit
patch. I however doubt it would be accepted, since it's possible that
that behaviour is by design (or by specification - after all, my
Linux installation is not very recent). That returns us to original
question. If it annoyed you, sorry.


CF> cgf



--
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