X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=tFKkoLolabgrODN3vCh4FHtQqEVX
	7SutX8j8BanjkGy5pXM/I3VXr9qbM40nQ1L29i1qaPVqPIPlp8Jvu3EMp3wuZuV8
	kwiKUd2a7C/Zfj1KyM9D+8yK4TM5wTuJYJbN2fKrYeUvZM3rZuxsNGd4v72Q808V
	MHcUK6G+xi1J/2U=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; s=default; bh=OA3fB5CM4ZpFv7/KY6nuEl8S8Q8=; b=x+
	VC784GYOQQT/+dSatBmgpmn/j/XXyc/uKIjmRdQz352rjcl29hdJGUA0QsiQSzkt
	mxJM9UIDy0CZFkIchvPXuam+jD1c5BssM3etkcsPT6b9y/P3Q+nDYaNq9pX5CrPH
	Yhlh+PImdI4t7yLZvxtFcKHF03B3QoGQK4arVSwMs=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=2.1 required=5.0 tests=AWL,BAYES_40,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=H*MI:sk:56E75B3, H*f:sk:56E75B3, raw, H*i:sk:56E75B3
X-HELO: etr-usa.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: ctrl-c doesn't reliably kill ping
From: Warren Young <wyml AT etr-usa DOT com>
In-Reply-To: <56E75B3E.7020102@farance.com>
Date: Tue, 15 Mar 2016 09:13:19 -0600
Message-Id: <AEE131C3-FC9F-44FF-BD10-A553B98F1826@etr-usa.com>
References: <56E6F25A DOT 7070000 AT gmx DOT de> <56E75B3E DOT 7020102 AT farance DOT com>
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u2FFDbRf015757

On Mar 14, 2016, at 6:45 PM, Frank Farance <frank AT farance DOT com> wrote:
> 
> 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]”.

Are you certain that you’re using the Cygwin ping, and not the native Windows ping?

Cygwin ping requires admin privileges, so you’d definitely know if you were using it.  In a non-Admin shell, you see:

  $ ping gw
  ping: socket: Operation not permitted

You can’t expect native Windows executables to respond in a POSIXy way to POSIX signals.

(As for “why” Cygwin ping requires admin privileges and native ping does not, it’s because native ping uses a special DLL that avoids the need for raw sockets.  Cygwin ping requires raw sockets in order to do things in a POSXYy way.)

> 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.

Use GRC’s DNS benchmark to find a DNS server that is not only fast but also standards-compliant:

  https://www.grc.com/dns/benchmark.htm

If you can’t be bothered, use Google’s DNS: 8.8.8.8 and 8.8.4.4.
--
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