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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=ZKDh+iKMZXxfUyYFPMGkomEHPDR9XDreQajBDs44a6t
	Q/owFVKa5VaN3Szh/5xWWpSWcqjml68v5bnSvSB6zVjm0IdOH5BDIxJagX2PiB/w
	BQsjaisGIypEDOqhz280xNymYBHtzlUTE1WKDPXRZS8aFJGiRMY15dMqJCwDV718
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=LJC18v0sI+AuGmK+UT7Vy55NAz8=; b=Kdpdc256iCHD2XYTg
	W5IO8iiNlsPr9XZpgS3nSRnq8GtN8J4FeMGvSpOm6z/mb7DHLc/L6kvuZr5DZXs9
	am9VqYkCXSvQT3cEvwS0j5inzJCN1l41llJwjLlNRipHdj8I4RYnqHcJ428lc0T7
	NDSi04Fw0V/NpKYJGUv0waU6Co=
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=0.8 required=5.0 tests=BAYES_50 autolearn=ham version=3.3.2 spammy=School, Answer, 2900, H*UA:Macintosh
X-HELO:	midtown.nycx.com
Message-ID:	<56EB1D2B.4090103@farance.com>
Date:	Thu, 17 Mar 2016 17:10:03 -0400
From:	Frank Farance <frank AT farance DOT com>
User-Agent:	Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: ctrl-c doesn't reliably kill ping
References:	<56E6F25A DOT 7070000 AT gmx DOT de> <56E75B3E DOT 7020102 AT farance DOT com> <54382838 DOT 20160315140038 AT yandex DOT ru> <9ee672500661e37c240d30d8413ca0af AT mail DOT kylheku DOT com> <56E972EB DOT 9000204 AT gmail DOT com> <CAOC2fq80JudLuzgtg+P-jCG5ZiS0jMNqTE86Tn3ynJm3=6kFSQ AT mail DOT gmail DOT com> <f9bfd813b9156f888a1571fb41c3ded5 AT mail DOT kylheku DOT com> <CAD8GWsvgv8e6BmJvximDM5oOKmqR=+EKzrmQXQMNfn612egdug AT mail DOT gmail DOT com>
In-Reply-To:	<CAD8GWsvgv8e6BmJvximDM5oOKmqR=+EKzrmQXQMNfn612egdug@mail.gmail.com>
X-IsSubscribed:	yes

Folks-

Thank you for the thoughtful observations, responses, and suggestions, which I 
will summarize:

- Suggestion #1: Try different DNS settings not using Verizon.
- Suggestion #2: Try different Verizon configuration.
- Suggestion #3: Try Windows version of ping.
- Observation #4: This shouldn't work unless I am administrator (FYI: I've 
configured the cygwin terminal to run as administrator).
- Question #5: Am I running the windows ping?  Answer: Nope, I did "type ping", 
which returned "/usr/bin/ping".

Regarding Verizon, and possibly different settings, my point was not to identify 
flaws in Verizon, I just wanted to give you background on the problem - and I 
believe people understand its nature.  I am well aware of well-known DNS 
servers, such as 8.8.8.8 and 8.8.4.4 -- I am Old School, so I still occasionally 
use the UUNET DNS caches 198.6.1.? to test stuff. :-)

Regarding incompatible ISPs, I believe the program should be robust enough to 
succeed, robust enough to fail, but it shouldn't hang and become non-interruptable.

So from a POSIX compatibility and operating system kernel perspective, I am 
surprised that it is possible to write an application program that gets into an 
non-interruptable state.  In traditional UNIX kernels, it was possible to get 
stuck in a *hard* wait (like local hard drive access), but I don't understand 
how this is possible with ping or any other network application.

Perhaps I don't understand the cygwin signal mechanism and someone can point me 
in the right direction for ping.  Perhaps someone can explain how ping can get 
into this state.

Anyway, as we'd say in standardizing the C programming language, this behavior 
is a "surprise" ... and we should look to eliminate "surprises".

Again, thank you in advance for your help.

-FF


-- 
______________________________________________________________________
Frank Farance, Farance Inc.    T: +1 212 486 4700   M: +1 917 751 2900
mailto:frank AT farance DOT 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

- Raw text -