Re: bin/53463: ping responds late to SIGINT

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR bin/53463; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: bin/53463: ping responds late to SIGINT
Date: Mon, 23 Jul 2018 19:46:05 +0700

     Date:        Mon, 23 Jul 2018 07:35:00 +0000 (UTC)
     From:        martin%NetBSD.org@localhost
     Message-ID:  <20180723073500.3362E7A264%mollari.NetBSD.org@localhost>
 
   | On NetBSD 8.0 this instantly brings back the shell prompt.
 
 Are you sure?   That's not how I remember it, more or less, forever.
 
 The SIGINT tells ping to stop sending, it then waits for replies to the last
 packets it sent (anything outstanding) calculates the stats on what was
 sent/received ... etc, prints the results, and exits.
 
 You're right that if it takes a long time for anything to be returned (lost
 packets, or ICMP filtering, or just infrequent ICMP) then ping will wait
 quite a while before giving up.   When that happens, a second SIGINT
 has traditionally caused ping to treat the missing replies as lost packets
 (immediately) and exit.
 
 kre