In message <[EMAIL PROTECTED]>, "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 <date> 
and OpenSSH 2.3.0.


Regards,                         Phone:  (250)387-8437
Cy Schubert                        Fax:  (250)387-5766
Team Leader, Sun/Alpha Team   Internet:  [EMAIL PROTECTED]
Open Systems Group, ITSD, ISTA
Province of BC





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Reply via email to