From owner-freebsd-stable Sun Feb 11 0: 0:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from level3.dynacom.net (level3.dynacom.net [206.107.213.213]) by hub.freebsd.org (Postfix) with SMTP id 8629037B401 for ; Sat, 10 Feb 2001 23:59:51 -0800 (PST) Received: (qmail 20051 invoked by uid 0); 11 Feb 2001 07:59:50 -0000 Received: from dsl1-160.dynacom.net (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 11 Feb 2001 07:59:50 -0000 Message-ID: <3A864675.3A752582@urx.com> Date: Sat, 10 Feb 2001 23:59:49 -0800 From: Kent Stewart X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: Blaz Zupan Cc: Matt Dillon , Andrew.Hodgkins@hurlburt.af.mil, freebsd-stable@FreeBSD.ORG Subject: Re: Proposed makewhatis perl script fix References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Blaz Zupan wrote: > > > :Actually, I don't think it fixed everything. There have been ports > > :that also had problems with piping to tar and broken pipes. It > > :wouldn't surprise me if the makewhatis problem was only a little piece > > :of what is broken. > > : > > :Kent > > > > makewhatis is just makewhatis... it has nothing to do with tar. > > > > When you tar something up, tar writes full blocks. But when you untar > > something the actual end of the archive may occur in the middle of a > > block. tar will close the input descriptor 'early' in this case, > > potentially before gunzip or uncompress manage to write the last block > > of zeros. > > I also don't believe that this is the real fix - there is something fishy > going on in stable. I just upgraded all of our servers from 4.2-RELEASE to > 4.2-STABLE and I see the following messages upon installing *any* package: > > /home/blaz# pkg_add gmake-3.79.1.tgz > > gzip: stdout: Broken pipe > tar: child returned status 1 > /home/blaz# > > The package actually appears to install and work fine. I also noticed similar > messages from gzip during "make" on a port, but again the port built and > installed fine after that. > > So no, your makewhatis patch only appears to be a bandaid, but there is > something going on deeper (possibly in the kernel) that was not there in > 4.2-RELEASE. Were you using ssh to login on to the computers when you were doing the package/port work? That seems to be the common thread from my end. At least, the broken pipes didn't start occuring until the version of Openssh was updated. If I telnet and do my work no problem; however, if I use ssh, then I see broken pipes. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html http://daily.daemonnews.org/ SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message