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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=MN56+fQIfE0jSGm0
	PBrzd7tytF+/XkAiNEtyjFLYyFjBA9K9Ddo7ZDwEpZZL3NEJO3zSgVcbRmiLMoGV
	5aD8qpYnTwca8T2X7MrRCgm7RwH7YpmGnMgIhKKJ0K9rbV15Mz3dE/fo/yz/7v17
	QnFFMDG9sBrWR8qAzlAVC0Dq53I=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=1Q+G5BSAD4mx0BRx0frszT
	Zz8TQ=; b=Oh3LGqyMHqekTPdDl5f5caemt01vWMcdQdRcIc1BslK4VnVdj7cfkH
	Wpzkzb0+DpakvQrVrhQPsKgLxqfAk7BdLmNZWdqeH0TEOk9fxcLKGG2O4Ujln/bD
	EDsYsxbhHQaj6/mCyT2yh+TxGyg9eB9Wx+NuMqV+CvYFVpBh5414s=
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.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*MI:sk:56E75B3, Hx-languages-length:1607, H*i:sk:56E75B3, hanging
X-HELO:	mail-wm0-f54.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=dk+D5AMl6kexh7UHAh00aZRovCofjz+LW/fX68tFF44=; b=MmSARFJE6n3ZenVVTPjFsPAaIf67y1o0bvfgDpfZ6QSw/paZCjuOEi05kBKopjZ6IL pABNDff+N9myqE6IYpUkCJMmhHRExUoFDnf9XWqjGnJiFJbDGS9m8bSNQVaBhl0/FjmR b3tHItwdO00aXVBoOy8HXzf4eoImpxUFmrJSlMqq9LwM3m2eJNX62b5HD+SvG3D8X+6W sRdwTQMDkyl1m+4NDhzYUEHw+D9epPh6swnDV6vsQLuiZ1AYMlraRsN02yHhgfz69rmR uWN8RVuswisReggKL8itNi1eIN4rL86Mf7GY4h3yA2RvSNbEW7I3whEmfgaRCX1Mb2vD dm2w==
X-Gm-Message-State:	AD7BkJJQsIgYiw+Yg8FmWIjaIFOHQGnVA9hl5JXlOsAIUjBdjQp3DcmE0mpGQma9vZXcOw==
X-Received:	by 10.28.48.136 with SMTP id w130mr30733312wmw.54.1458134700837; Wed, 16 Mar 2016 06:25:00 -0700 (PDT)
Subject:	Re: ctrl-c doesn't reliably kill ping
To:	cygwin AT cygwin DOT com
References:	<56E6F25A DOT 7070000 AT gmx DOT de> <56E75B3E DOT 7020102 AT farance DOT com>
From:	Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID:	<56E95EA2.8070800@gmail.com>
Date:	Wed, 16 Mar 2016 14:24:50 +0100
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:	<56E75B3E.7020102@farance.com>
X-IsSubscribed:	yes

On 15/03/2016 01:45, Frank Farance 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]".
>
>
> Back to the problem, so when I type
>
> $ ping some.unknown.host
>

I do not succeed to replicate.
CTRL-C works fine for me

$ type ping
ping is hashed (/usr/bin/ping)

$ ping 172.21.1.254
PING 172.21.1.254 (172.21.1.254): 56 data bytes

----172.21.1.254 PING Statistics----
4 packets transmitted, 0 packets received, 100.0% packet loss

or I have not a biased DNS answer.

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

cygwin ping is based on very old source from a time where people was not
cheating on protocol answer.

http://ftp.arl.mil/mike/ping.html
(the author passed away 16 years ago..)

can you send me a strace to see where the program is stacking ?
No promise to find a solution but I will look on it.

Regards
Marco





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