From owner-freebsd-stable Mon Mar 5 14: 6: 6 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 A2CC637B721 for ; Mon, 5 Mar 2001 14:05:45 -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 f25M5b619877; Mon, 5 Mar 2001 17:05:37 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.0.2.1.0.20010305164530.023ce320@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Mon, 05 Mar 2001 16:59:45 -0500 To: Carson Gaspar From: Mike Tancsa Subject: Re: more strange problem with broken pipes and ssh Cc: stable@FreeBSD.ORG In-Reply-To: <45119937.983800045@[10.10.1.2]> References: <200103040318.TAA25378@salsa.gv.tsc.tdk.com> <200103040318.TAA25378@salsa.gv.tsc.tdk.com> 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 01:47 PM 3/5/01 -0800, Carson Gaspar wrote: >Any app that cares about SIGPIPE should set it appropriately. If >makewhatis and grep don't, please fix makewhatis and grep. That _doesn't_ >mean that we shouldn't make sure SSH leaves things mostly the same way >other login sessions do, just that we should _also_ fix broken programs. I dont pretend to fully understand the nature of the problem, but if its an issue with the app, why does this not surface when connecting with older versions sshd, nor with telnetd or rlogind ? Also, if you login physically on the console, its different than logging in over the network. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message