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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=Dt
	YhMhEudAhlyCaQ3oj5CQdSD8ZOU7gtx9Q2b7m5hY3cF6/TIp0wExM49gTJJn/a9Y
	Tc5/tNAB3m9xYoWTft8qiEkmV4cW1pjT9Nf8a14iyitoWyPoijKZsg8SP6Iz0SJ8
	DRKq0HBHPH/BfrFkHLyPzog0nv2bl/ldv+ySVcEK8=
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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=4WfaLHJR
	hNoJDL24d60EoRsKppw=; b=DIsFYhtfHH4OlFR2FJ/pOrB066B+ivap7Q0o21iJ
	9kNGlde4rdDF83bKNOge7rlzv2HnWe6eYkPUKAFv4RRIiT6sY1cmCSUvJ+xukOqD
	kH7uYjWBk6ICrFn/ONnMRe7Gx/r/8pJiY7hjL0I1NuYMikzfrSn0LbhPp5x6E3Si
	+Yg=
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.3 required=5.0 tests=AWL,BAYES_50,KAM_INFOUSMEBIZ,RP_MATCHES_RCVD,SPF_PASS autolearn=no version=3.3.2
X-HELO: alum-mailsec-scanner-5.mit.edu
MIME-Version: 1.0
X-Received: by 10.50.119.10 with SMTP id kq10mr1906385igb.59.1448477482758; Wed, 25 Nov 2015 10:51:22 -0800 (PST)
In-Reply-To: <56559566.7070808@gmail.com>
References: <01f501d12701$d5af6fb0$810e4f10$@vianet.ca>	<5654E4E3 DOT 8050605 AT gmail DOT com>	<56555DF4 DOT 9090804 AT towo DOT net>	<56559566 DOT 7070808 AT gmail DOT com>
Date: Wed, 25 Nov 2015 11:51:22 -0700
X-Gmail-Original-Message-ID: <CAK-n8j5VV6n8UC_uNkKZX25m3K-iv2cp4WjZs6r6_2Xipfas0g AT mail DOT gmail DOT com>
Message-ID: <CAK-n8j5VV6n8UC_uNkKZX25m3K-iv2cp4WjZs6r6_2Xipfas0g@mail.gmail.com>
Subject: Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host
From: Jim Reisert AD1C <jjreisert AT alum DOT mit DOT edu>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes

On Wed, Nov 25, 2015 at 4:03 AM, Marco Atzeri wrote:

> you are right is not a mintty only issue.
> Same happens in xterm
>
>
> $ which ping
> /usr/bin/ping
>
> $ ping 2.2.2.2
> PING 2.2.2.2 (2.2.2.2): 56 data bytes
>
> It sticks here forever, CTRL+C ineffective.

Worked fine for me using Cygwin64 and Cygwin build 2.4.0(0.292/5/3)

[LTDENA-REISERT:~] $ ping 2.2.2.2

Pinging 2.2.2.2 with 32 bytes of data:

(type CTRL-C here)

[LTDENA-REISERT:~] $


-- 
Jim Reisert AD1C, <jjreisert AT alum DOT mit DOT edu>, http://www.ad1c.us

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