From owner-freebsd-stable Fri Mar 2 14:26: 8 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 126D237B718 for ; Fri, 2 Mar 2001 14:26:04 -0800 (PST) (envelope-from kstewart@urx.com) Received: (qmail 8237 invoked by uid 0); 2 Mar 2001 22:26:03 -0000 Received: from unknown (HELO urx.com) (206.159.132.160) by mail.urx.com with SMTP; 2 Mar 2001 22:26:03 -0000 Message-ID: <3AA01DFA.C56DBAE@urx.com> Date: Fri, 02 Mar 2001 14:26:02 -0800 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mike Tancsa Cc: Cy Schubert - ITSD Open Systems Group , stable@FreeBSD.ORG Subject: Re: more strange problem with broken pipes and ssh References: <5.0.2.1.0.20010302093140.0365e570@marble.sentex.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Tancsa wrote: > > At 06:32 AM 3/2/01 -0800, Cy Schubert - ITSD Open Systems Group wrote: > >In message <5.0.2.1.0.20010226143727.024d0c90@marble.sentex.ca>, 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 majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message