Cygwin piping misbehaviour

Cygwin piping misbehaviour

[Paul Sokolovsky]

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@sourceware.cygnus.com

Re: Cygwin piping misbehaviour

[Chris Faylor]

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

Re[2]: Cygwin piping misbehaviour

[Paul Sokolovsky]

Hello Chris,

Chris Faylor <cgf@cygnus.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@sourceware.cygnus.com