From owner-freebsd-stable  Fri Mar  2  6:47:37 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4])
	by hub.freebsd.org (Postfix) with ESMTP id B61BF37B718
	for <stable@FreeBSD.ORG>; Fri,  2 Mar 2001 06:47:30 -0800 (PST)
	(envelope-from mike@sentex.net)
Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47])
	by smtp1.sentex.ca (8.11.2/8.11.1) with ESMTP id f22EkRF64004;
	Fri, 2 Mar 2001 09:46:27 -0500 (EST)
	(envelope-from mike@sentex.net)
Message-Id: <5.0.2.1.0.20010302093140.0365e570@marble.sentex.ca>
X-Sender: mdtpop@marble.sentex.ca
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Fri, 02 Mar 2001 09:39:57 -0500
To: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>
From: Mike Tancsa <mike@sentex.net>
Subject: Re: more strange problem with broken pipes and ssh 
Cc: stable@FreeBSD.ORG
In-Reply-To: <200103021433.f22EXHS61992@cwsys.cwsent.com>
References: <Your message of "Mon, 26 Feb 2001 14:58:07 EST." <5.0.2.1.0.20010226143727.024d0c90@marble.sentex.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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.

         ---Mike


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message