From owner-freebsd-current Fri Jul 25 12:21:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA19440 for current-outgoing; Fri, 25 Jul 1997 12:21:26 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA19430 for ; Fri, 25 Jul 1997 12:21:18 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA07993; Fri, 25 Jul 1997 11:59:18 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd007988; Fri Jul 25 18:59:12 1997 Message-ID: <33D8F70D.63DABEB6@whistle.com> Date: Fri, 25 Jul 1997 11:57:17 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: John Polstra CC: current@FreeBSD.ORG Subject: Re: Whats happened to ping? References: <199707251537.KAA28194@ns.tar.com> <199707251636.JAA00656@austin.polstra.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John Polstra wrote: > > > It seems that there have recently been changes to the sematics of > > "ping -c N". Unless I'm mistaken, the old behavior was that "ping -c N" > > meant try to send N packets. Now it means keep trying until N packets > > are actually sent. > > > > The practical effect of this is that "ping -c N" might loop endlessly, > > if, for example, the network is down and the sendto fails. > > 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. > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth this was a case we tested.. sean? bruce? I think we need to re-open the patient...