From nobody  Sat Apr  4 18:48:57 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA10107;
          Sat, 4 Apr 1998 18:48:57 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199804050248.SAA10107@hub.freebsd.org>
Date: Sat, 4 Apr 1998 18:48:57 -0800 (PST)
From: tomj@malkavian.org
To: freebsd-gnats-submit@freebsd.org
Subject: ping sometimes cannot be killed with a Control-C
X-Send-Pr-Version: www-1.0

>Number:         6214
>Category:       bin
>Synopsis:       ping sometimes cannot be killed with a Control-C
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Apr  4 18:50:01 PST 1998
>Closed-Date:    Sat May 20 21:29:59 PDT 2000
>Last-Modified:  Sat May 20 21:32:16 PDT 2000
>Originator:     Tom Jobbins
>Release:        2.2.6-STABLE
>Organization:
>Environment:
FreeBSD kria.netkonect.co.uk 2.2.6-STABLE FreeBSD 2.2.6-STABLE:
Thu Apr 2 00:02:35 BST 1998 root@kria.netkonect.co.uk:/usr/src/sys/compile/JIMI i386
>Description:
ping sometimes cannot be killed by issuing a Control-C - it has to
be killed with a 'kill <pid>' instead.  This seems to happen particularly
when pinging a site that is not responding, or when leaving a ping
running for some time.
>How-To-Repeat:
Ping a site that doesn't respond.
>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: hoek 
State-Changed-When: Sat May 20 21:29:59 PDT 2000 
State-Changed-Why:  
Problem was: "Ping sometimes becomes unresponsive to Ctrl-C" 

I haven't seen this problem for over a year, now.  I remember when 
it started, I saw it quite frequently.  It seems to be a fair assumption 
that the problem has fixed itself.  If anyone still sees this on4.0 
or later, please say so in order that I may re-open this PR. 
>Unformatted:
