Date: Sun, 11 Feb 2001 17:45:31 +0300 From: "Valeriy E. Ushakov" <uwe@ptc.spbu.ru> To: freebsd-stable@freebsd.org Subject: Re: Proposed makewhatis perl script fix Message-ID: <20010211174531.A9773@snark.ptc.spbu.ru> In-Reply-To: <200102111426.f1BEQ3K98277@cwsys.cwsent.com>; from "Cy Schubert - ITSD Open Systems Group" on Sun, Feb 11, 2001 at 06:25:44 References: <3A864675.3A752582@urx.com> <200102111426.f1BEQ3K98277@cwsys.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
SY, Uwe
--
uwe@ptc.spbu.ru | Zu Grunde kommen
http://www.ptc.spbu.ru/~uwe/ | Ist zu Grunde gehen
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010211174531.A9773>