From owner-freebsd-stable Sun Feb 11 6:57:44 2001 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id AF5E737B401 for ; Sun, 11 Feb 2001 06:57:41 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id GAA12265; Sun, 11 Feb 2001 06:56:47 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda12263; Sun Feb 11 06:56:37 2001 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.2/8.9.1) id f1BEuWd77665; Sun, 11 Feb 2001 06:56:32 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdw77663; Sun Feb 11 06:56:07 2001 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.2/8.9.1) id f1BEu7r98447; Sun, 11 Feb 2001 06:56:07 -0800 (PST) Message-Id: <200102111456.f1BEu7r98447@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdL98442; Sun Feb 11 06:55:56 2001 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: schubert To: "Valeriy E. Ushakov" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Proposed makewhatis perl script fix In-reply-to: Your message of "Sun, 11 Feb 2001 17:45:31 +0300." <20010211174531.A9773@snark.ptc.spbu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Feb 2001 06:55:56 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010211174531.A9773@snark.ptc.spbu.ru>, "Valeriy E. Ushakov" write s: > On Sun, Feb 11, 2001 at 06:25:44 -0800, Cy Schubert wrote: > > > > > 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. > > > > Could it be some interaction between -STABLE and OpenSSH 2.3.0? I > > installed OpenSSH 2.3.0 on some 4.2-RELEASE systems, including the > > src/secure bits, and have had no broken pipes problems when using ssh. > > Well, in Russian BSD newsgroup I see complaints that even > > $ program | more # and press `q' while program is still running > > giving the same error. > > OTOH, I have -STABLE as of Feb 3 (i.e. with openssh 2.3.0) on my home > box and I do *not* see this problem when I slogin to it from office. Based upon what I've seen on this list and my own empirical evidence, I think it must be combination of conditions, e.g. -STABLE as of and OpenSSH 2.3.0. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/Alpha Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message