From owner-freebsd-stable Sun Feb 11 0:42:46 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pit.databus.com (p101-45.acedsl.com [160.79.101.45]) by hub.freebsd.org (Postfix) with ESMTP id 01F4037B503 for ; Sun, 11 Feb 2001 00:42:25 -0800 (PST) Received: (from barney@localhost) by pit.databus.com (8.11.1/8.11.1) id f1B8fmd52008; Sun, 11 Feb 2001 03:41:48 -0500 (EST) (envelope-from barney) Date: Sun, 11 Feb 2001 03:41:48 -0500 From: Barney Wolff To: Blaz Zupan Cc: Matt Dillon , Andrew.Hodgkins@hurlburt.af.mil, kstewart@urx.com, freebsd-stable@FreeBSD.ORG Subject: Re: RE: Proposed makewhatis perl script fix Message-ID: <20010211034147.A51972@pit.databus.com> References: <200102110819.f1B8Jk430590@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from blaz@amis.net on Sun, Feb 11, 2001 at 09:35:43AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Er, could it possibly be that telnet has been hiding the error all along? It's really, really hard to see how ssh could *create* this sort of error. Barney Wolff On Sun, Feb 11, 2001 at 09:35:43AM +0100, Blaz Zupan wrote: > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message