From owner-freebsd-stable Sun Feb 11 0:36: 1 2001 Delivered-To: freebsd-stable@freebsd.org Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by hub.freebsd.org (Postfix) with ESMTP id CE37437B401 for ; Sun, 11 Feb 2001 00:35:44 -0800 (PST) Received: by titanic.medinet.si (Postfix, from userid 1000) id 0509226C06; Sun, 11 Feb 2001 09:35:43 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by titanic.medinet.si (Postfix) with ESMTP id E818D11708; Sun, 11 Feb 2001 09:35:43 +0100 (CET) Date: Sun, 11 Feb 2001 09:35:43 +0100 (CET) From: Blaz Zupan To: Matt Dillon Cc: , , Subject: Re: RE: Proposed makewhatis perl script fix In-Reply-To: <200102110819.f1B8Jk430590@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > pkg_add runs tar with the --fast-read option to extract the table of > contents. When I remove the option pkg_add no longer reports broken > pipes. When gunzip'ing piped to tar, and tar exits early due to > the option, gunzip properly gets a 'gzip: stdout: Broken pipe' error. > > Maybe 'tar' was changed recently, maybe 'gunzip' was changed recently, > I don't know. But it isn't a kernel problem. The kernel is doing > exactly what it is supposed to be doing. A simple "cvs diff" between RELENG_4_2_0_RELEASE and RELENG_4 reveals, that gzip has not changed at all, while tar has only grown bzip2 support. As Kent suggests, ssh might be the problem. To verify, I have just logged in through telnet and done a "pkg_add gmake-3.79.1.tgz". And yes indeed, the broken pipe message disappears. So the OpenSSH 2.3.0 seems to be causing the problem. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message