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: <42DE0998.DB8F6E09@dessent.net> Date: Wed, 20 Jul 2005 01:21:44 -0700 From: Brian Dessent MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: man - broken pipe References: 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: > After some updates I get broken pipe messages when pressing 'q' to exit > from less. The man pages are printed correctly. I think that is by design and not a bug. When you are viewing the manpage, a pipeline of commands has been setup to decompress and format the manpage. Because 'less' doesn't ask for more input until you page down, it means that those commands are all blocked waiting to consume their input and produce more output. If you quit 'less' before reaching the end, the pipeline is broken and the commands all receive SIGPIPE. It's normal and harmless. If you don't want to see the message you can hit 'end' or '>' before quitting less. It doesn't happen with small manpages because they probably fit entirely in a single buffer. 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/