This is the mail archive of the
mailing list for the Cygwin project.
Re: ctrl-c doesn't reliably kill ping
- From: Warren Young <wyml at etr-usa dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Tue, 15 Mar 2016 09:13:19 -0600
- Subject: Re: ctrl-c doesn't reliably kill ping
- Authentication-results: sourceware.org; auth=none
- References: <56E6F25A dot 7070000 at gmx dot de> <56E75B3E dot 7020102 at farance dot com>
On Mar 14, 2016, at 6:45 PM, Frank Farance <firstname.lastname@example.org> 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:
If you canât be bothered, use Googleâs DNS: 22.214.171.124 and 126.96.36.199.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple