Mike Tancsa wrote:
>
> At 06:32 AM 3/2/01 -0800, Cy Schubert - ITSD Open Systems Group wrote:
> >In message <[EMAIL PROTECTED]>, Mike
> >Tancsa wr
> >ites:
> > >
> > > OK, here is another strange problem with SSH and pipes. When connecting
> > > via some means other than ssh, the commands
> > >
> > > grep reject /var/log/maillog | less
> > >
> > > displays data as expected. However, when connected via ssh, hitting q to
> > > exit from less, I get a whole mess of
> > >
> > > grep: writing output: Broken pipe
> > > grep: writing output: Broken pipe
> > > grep: writing output: Broken pipe
> > > grep: writing output: Broken pipe
> > >
> > > This is with stable as of today and the problem showed up since the last
> > > ssh commits. The amount of broken pipes seems to scale with the amount of
> > > data less has, and it seems you need at least more than a screen full.
> >
> >I'm using -stable as of Feb 27 04:15 PST. No problems here. Is there
> >something in your ssh config that might either cause this bug to
> >manifest itself?
>
> If I recall you never had the problem with the makewhatis script and ssh as
> well due to some special config of your ssh (Kerberos?) ? This is with
>
> 4.2-STABLE FreeBSD 4.2-STABLE #0: Mon Feb 26
>
> Like the problem with the makewhatis broken pipes (and certain ports), the
> problem does not show itself when connecting to the machine via telnet or
> rlogin.
I had some broken pipe messages when I tried to upgrade to kde-2.1. I
backed up and telneted in and finished the install.
Kent
>
> ---Mike
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
--
Kent Stewart
Richland, WA
mailto:[EMAIL PROTECTED]
http://kstewart.urx.com/kstewart/index.html
FreeBSD News http://daily.daemonnews.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
