From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 38689 invoked by alias); 15 Mar 2016 00:46:00 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 38675 invoked by uid 89); 15 Mar 2016 00:45:59 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=BAYES_50 autolearn=ham version=3.3.2 spammy=751, H*Ad:U*frank, 2900, H*MI:sk:56E6F25 X-HELO: midtown.nycx.com Received: from midtown.nycx.com (HELO midtown.nycx.com) (192.104.18.21) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 15 Mar 2016 00:45:58 +0000 Received: from [192.168.1.2] (pool-173-52-48-88.nycmny.fios.verizon.net [173.52.48.88]) (authenticated bits=0) by midtown.nycx.com (8.13.7/8.13.7) with ESMTP id u2F0jn1L001904; Mon, 14 Mar 2016 20:45:49 -0400 Subject: ctrl-c doesn't reliably kill ping To: cygwin@cygwin.com References: <56E6F25A.7070000@gmx.de> From: Frank Farance Message-ID: <56E75B3E.7020102@farance.com> Date: Tue, 15 Mar 2016 00:46:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56E6F25A.7070000@gmx.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-03/txt/msg00226.txt.bz2 I have been having this problem with "ping". If I "ping" a location that doesn't exist, then "ping" just hangs and cannot be killed via "kill -KILL [pid]". A little digression, so you understand the background ... The workstation I am doing this from is connected to a Verizon router to their FIOS network. Now the reason I mention this is that the router's DNS (via DHCP to my workstation) is 192.168.1.1, which I presume is forwarded from the router upstream to Verizon's DNS caches. So if I type the URL http://something.that.doesnt.exist in my browser, rather than getting a Hostname Not Found error (at the name resolution level), it actually loads up a page saying "something.that.doesnt.exist" isn't found and then I have a Yahoo set of search results on things matching the broken hostname. So all of this is normal ISP stuff: they actually resolve unknown addresses to their own website (which is 90.242.140.21). Ok, ending the digression .... Back to the problem, so when I type $ ping some.unknown.host according to "ping", the hostname resolves to 90.242.140.21 (as per the explanation above), but I cannot kill "ping". I tried "ping" with a limited packet size and count so, in theory, "ping" would die on its own after 10 packets, such as: $ ping some.unknown.host 50 10 but it still hangs rather than timing out. If I ping to some actual IP address that is unresponsive (route-able to the last subnet, but dies on the floor at the end), then I can kill via ctrl-c. My only solution to the hanging "ping" is to kill the terminal window. Any suggestions on: - Why "ping" behaves this way? - How to avoid this problem? Thanks, in advance. -FF -- ______________________________________________________________________ Frank Farance, Farance Inc. T: +1 212 486 4700 M: +1 917 751 2900 mailto:frank@farance.com http://farance.com Standards/Products/Services for Information/Communication Technologies -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple