Subject: Re: bin/5103: SIGPIPE related bugs in 1.3
To: None <firstname.lastname@example.org>
From: Giles Lean <email@example.com>
Date: 03/03/1998 23:41:05
On Tue, 3 Mar 1998 01:07:00 -0500 (EST) firstname.lastname@example.org wrote:
> If you run something resembling the following command where the fgrep
> will find many more lines of output than just one page, and you quit
> 'less' after the first page you'll get many "fgrep: writing output:
> Broken pipe" errors:
> fgrep 'common-string' lots and lots of files | less
I found this or something similar when upgrading a i386 1.1 machine to
1.3 at the weekend.
$ (cd /some/place; tar cf - .) | tar xpvf -
tar: can't write to - : Broken pipe
In this case the writing side is writing a bunch of \0's that the
reading side doesn't want, so SIGPIPE might be entirely correct.
All the data was transferred correctly.
I can't reproduce the problem in -current, however my -current machine
runs diskless and is using UVM and PMAP_NEW so there are some