Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-Id:	<6.1.2.0.1.20040929001114.03ec1eb0@mail.ros.com.au>
X-Sender:	errol AT mail DOT ros DOT com DOT au (Unverified)
Date:	Wed, 29 Sep 2004 00:17:08 +1000
To:	cygwin mailing-list <cygwin AT cygwin DOT com>
From:	Errol Smith <errol AT ros DOT com DOT au>
Subject:	Re: "Broken pipe" warning from bash.
In-Reply-To:	<n2m-g.cjbbtl.3vveifr.1@buzzy-box.bavag>
References:	<n2m-g DOT cjbbtl DOT 3vveifr DOT 1 AT buzzy-box DOT bavag>
Mime-Version:	1.0
X-IsSubscribed:	yes

At 05:53 PM 28/09/2004, Bas van Gompel wrote:
>Following little (bash) shell-script many times causes a "Broken pipe"
>(SIGPIPE) warning to be emitted by bash. Is this expected behaviour?
>
>An example of the message:
>./tc-pipe.sh: line 5: 3541109 Broken pipe             seq 1 2
>
>The message is generated on the second pass through the loop.
>Changing ``a b'' to ``a b c d e'' below, often prints the message 4
>times.
>
>=== Begin tc-pipe.sh ===
>#!/bin/bash
>
>for t in a b; do
>  seq 1 2
>done | head -n 1
>
>==== End tc-pipe.sh ====

  I was going to say "use a recent snapshot because the 'Broken Pipe' 
problems were fixed by the Gold-Star deserving Pierre"... BUT I tried your 
testcase and it fails (intermittently) even with the latest snapshot 
(20040928).
  Pierre's patch DID fix the broken pipe issues I reported so this might be 
a different problem.

Errol


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -