This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Cygwin piping misbehaviour
- To: cygwin at sourceware dot cygnus dot com
- Subject: Re: Cygwin piping misbehaviour
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Mon, 13 Mar 2000 11:01:27 -0500
- References: <3611.000313@is.lg.ua>
- Reply-To: cygwin at sourceware dot cygnus dot com
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@sourceware.cygnus.com