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 From: Chris Faylor <cgf AT cygnus DOT com> Date: Mon, 13 Mar 2000 11:01:27 -0500 To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Cygwin piping misbehaviour Message-ID: <20000313110127.F1005@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, cygwin AT sourceware DOT cygnus DOT com References: <3611 DOT 000313 AT is DOT lg DOT ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: <3611.000313@is.lg.ua>; from paul-ml@is.lg.ua on Mon, Mar 13, 2000 at 02:40:52PM +0200 On Mon, Mar 13, 2000 at 02:40:52PM +0200, Paul Sokolovsky wrote: > 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. You're a programmer, right? And you have source code available... cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com