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 Message-ID: From: Bas van Gompel Subject: Re: "Broken pipe" warning from bash. References: In-Reply-To: Reply-To: cygwin mailing-list Organisation: Ehm... User-Agent: slrn/0.9.8.0 (Win32) Hamster/2.0.5.5 To: cygwin AT cygwin DOT com Lines: 29 Date: Wed, 29 Sep 2004 05:34:15 +0200 (MET DST) X-IsSubscribed: yes 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...) Sorry about the noise, ppl. L8r, Buzz. -- ) | | ---/ ---/ Yes, this | This message consists of true | I do not -- | | / / really is | and false bits entirely. | mail for ) | | / / a 72 by 4 +-------------------------------+ any1 but -- \--| /--- /--- .sigfile. | |perl -pe "s.u(z)\1.as." | me. 4^re -- 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/