From owner-freebsd-current  Mon May 11 06:40:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA10113
          for freebsd-current-outgoing; Mon, 11 May 1998 06:40:11 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (mothra.kralizec.net.au [203.15.68.22] (may be forged))
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA10106
          for <current@freebsd.org>; Mon, 11 May 1998 06:40:06 -0700 (PDT)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA21821
	for current@freebsd.org; Mon, 11 May 1998 23:38:06 +1000
Date: Mon, 11 May 1998 23:38:06 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199805111338.XAA21821@godzilla.zeta.org.au>
To: current@FreeBSD.ORG
Subject: Broken pipe errors
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I have been getting a lot of errors like "gzip: stdout: Broken pipe"
from `tar zx...' and "gzcat: stdout: Broken pipe" from makewhatis
lately.  These seem to be correct (tar really does stop reading from
stdin before gzip is finished), but I'd like to know why they just
started becoming common.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message