X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 19 Apr 2010 20:49:56 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Spurious 'grep: writing output' in Cygwin 1.7.5-1 in certain cases Message-ID: <20100420004956.GB7180@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4BCCE953 DOT 90204 AT redhat DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BCCE953.90204@redhat.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Mon, Apr 19, 2010 at 05:37:55PM -0600, Eric Blake wrote: >[adding bug-grep] > >On 04/19/2010 03:19 PM, Matthew Kidd wrote: >> We are seeing grep emit 'grep: writing output' multiple times in >> certain cases where the output of grep is piped to another program. >> Specifically, we see it in the following cases: >> >> grep thisandthat foo.txt | head >> grep thisandthat foo.txt | less > >Expected, if you are blocking SIGPIPE, although it might be improved a >bit. Grep is telling you that it encountered a write failure due to >EPIPE, and is thus about to exit with non-zero status. Did you paste >the full error message? On Linux, I see: > >grep: writing output: Broken pipe Apparently grep isn't seeing an actual EPIPE here for some reason. I will look into why that is the case. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple