From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: Re: ctrl-c doesn't reliably kill ping
Date: Wed, 16 Mar 2016 17:52:00 -0000 [thread overview]
Message-ID: <CAD8GWssCEcFQmrqso0UXgDuA07vuTK-4ZfVvbrMsRDFzapXivw@mail.gmail.com> (raw)
In-Reply-To: <8D39BB0F-A716-4F56-AF2D-D6C928266F5A@etr-usa.com>
On 3/16/16, Warren Young <wyml@etr-usa.com> wrote:
> On Mar 16, 2016, at 10:07 AM, Lee <ler762@gmail.com> wrote:
>>
>> The last time I tried the cygwin ping program it didn't return a
>> failure status
>
> It does if you don’t Ctrl-C out of it. So, if you’re using it from a
> script, you just ask for one packet:
>
> # ping does.not.exist 1 1
> ping: unknown host does.not.exist
> # echo $?
> 1
Thanks for the info - nice to know that the cygwin version of ping is
getting better.
Not that it's going to make any difference to me & my scripts, but
$ which ping
/cygdrive/c/windows/system32/ping
$ ping www.examle.com
Pinging www.examle.com [69.172.201.208] with 32 bytes of data:
Request timed out.
Request timed out.
<crtl>C
$ echo $?
130
> Note my fine new # prompt, indicating an admin shell, which has been
> required for Cygwin ping from the very beginning[1] due to the restrictions
> on raw sockets added in Windows XP SP2.
I've had a windows admin account for doing admin type things and a
user account with no special/extra privs for normal use ever since I
started using Win-XP, so the requirement to be running as admin (or
answer a UAC prompt) puts cygwin ping into the "does not meet my
needs" category.
> Windows ping gets around this by
> special dispensation of the kernel.[2]
>
> If you want to say Cygwin ping is “useless” because of that,
My apologies. If I offended you or anyone else it wasn't intentional.
I should have done a better job with my wording :(
Best Regards,
Lee
--
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
prev parent reply other threads:[~2016-03-16 17:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 17:18 ctrl-c doesn't reliably kill applications Björn Stabel
2016-03-14 23:39 ` Kaz Kylheku
2016-03-15 0:46 ` ctrl-c doesn't reliably kill ping Frank Farance
2016-03-15 11:05 ` Andrey Repin
2016-03-15 11:43 ` Adam Dinwoodie
2016-03-16 14:46 ` cyg Simple
2016-03-16 4:56 ` Kaz Kylheku
2016-03-16 11:50 ` Andrey Repin
2016-03-16 14:51 ` cyg Simple
2016-03-16 15:57 ` Michael Enright
2016-03-16 17:33 ` Kaz Kylheku
2016-03-16 18:10 ` Lee
2016-03-17 21:10 ` Frank Farance
2016-03-17 21:29 ` Marco Atzeri
2016-03-15 15:13 ` Warren Young
2016-03-16 13:25 ` Marco Atzeri
2016-03-17 20:04 ` ctrl-c doesn't reliably kill applications Björn Stabel
2016-04-18 21:38 ` Aaron Digulla
2016-04-19 9:13 ` Corinna Vinschen
2016-04-19 16:30 ` Aaron Digulla
2016-03-16 16:07 ` ctrl-c doesn't reliably kill ping Lee
2016-03-16 16:50 ` Warren Young
2016-03-16 17:52 ` Lee [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD8GWssCEcFQmrqso0UXgDuA07vuTK-4ZfVvbrMsRDFzapXivw@mail.gmail.com \
--to=ler762@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).