From owner-freebsd-stable Mon Feb 26 12: 4:15 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 5BAAF37B491 for ; Mon, 26 Feb 2001 12:04:13 -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 f1QK4Cv16119 for ; Mon, 26 Feb 2001 15:04:12 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.2.1.0.20010226143727.024d0c90@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 26 Feb 2001 14:58:07 -0500 To: stable@freebsd.org From: Mike Tancsa Subject: more strange problem with broken pipes and ssh 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 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. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message