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: <42DE10BC.8DF55946@dessent.net> Date: Wed, 20 Jul 2005 01:52:12 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: man - broken pipe References: <42DE0998 DOT DB8F6E09 AT dessent DOT net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Report: -5.9/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.0 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Krzysztof Duleba wrote: > I get this error on my laptop and only since I've updated most packages few > days ago. I don't get this on Linux boxes and on Windows box with Cygwin > updated the last month. > > Hitting 'end' or '>' helps indeed. I wonder what makes the difference that > now SIGPIPE is delivered and has visible effects. I think it would depend on what packages you upgraded. It could be that the default buffer size somewhere has changed. If it was quite large to begin with, and then was reduced, you would see the error more often. I don't think the SIGPIPE behavior itself has changed, it has always been the case that a writer to a broken pipe receives the signal. But it can be kind of racey if both the writer and reader are exiting. Or, it could be that bash 2.x supressed that message while bash 3.x doesn't. Brian -- 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/