Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 28 Sep 2004 23:37:14 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: "Broken pipe" warning from bash. (question for bash maintainer) Message-ID: <20040929033714.GA6825@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Wed, Sep 29, 2004 at 05:34:15AM +0200, Bas van Gompel wrote: >Op Tue, 28 Sep 2004 09:53:32 +0200 (MET DST) schreef ik > >: Following little (bash) shell-script many times causes a "Broken pipe" >: (SIGPIPE) warning to be emitted by bash. Is this expected behaviour? > >Maybe I should have been clearer... ... > >[Explanation I was writing snipped.] > >...It's in the bash FAQ... >section E2. > >According to that, defining ``DONT_REPORT_SIGPIPE'' in ``config-top.h'' >will enable building a version which does not show the behaviour. > >Is this flag set on the various distro's? > >Should it be set on cygwin? (If only to prevent more stupid questions >like mine...) It sounds like maybe it should be set. I've reset the subject to alert the bash maintainer. cgf -- 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/