From owner-freebsd-current Fri Jul 25 10:43:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA15123 for current-outgoing; Fri, 25 Jul 1997 10:43:32 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA15118 for ; Fri, 25 Jul 1997 10:43:29 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.6/8.8.5) with ESMTP id KAA01182 for ; Fri, 25 Jul 1997 10:43:23 -0700 (PDT) Message-Id: <199707251743.KAA01182@austin.polstra.com> To: current@freebsd.org Subject: Re: Whats happened to ping? In-Reply-To: <199707251636.JAA00656@austin.polstra.com> References: <199707251537.KAA28194@ns.tar.com> <199707251636.JAA00656@austin.polstra.com> Organization: Polstra & Co., Seattle, WA Date: Fri, 25 Jul 1997 10:43:23 -0700 From: John Polstra Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I wrote this, but it's wrong: > Also, if ping isn't receiving any replies, it's impossible to kill > it with a simple keyboard interrupt (SIGINT). I don't think that > was the case before. It fails like that under 2.2-stable, but not under -current. Thanks to sef for pointing out the mistake. Sorry for the bad information. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth