From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host
Date: Wed, 25 Nov 2015 19:52:00 -0000 [thread overview]
Message-ID: <56560930.70401@towo.net> (raw)
In-Reply-To: <CAK-n8j5VV6n8UC_uNkKZX25m3K-iv2cp4WjZs6r6_2Xipfas0g@mail.gmail.com>
Am 25.11.2015 um 19:51 schrieb Jim Reisert AD1C:
> 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:~] $
Please note the difference and provide the necessary information (`which
ping`):
> PING 2.2.2.2 (2.2.2.2): 56 data bytes
> Pinging 2.2.2.2 with 32 bytes of data:
------
Thomas
--
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
next prev parent reply other threads:[~2015-11-25 19:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 22:30 Jeff Hansen
2015-11-24 23:05 ` Marco Atzeri
2015-11-25 11:03 ` Thomas Wolff
2015-11-25 12:04 ` Marco Atzeri
2015-11-25 19:04 ` Jim Reisert AD1C
2015-11-25 19:52 ` Thomas Wolff [this message]
2015-11-25 20:35 ` Jim Reisert AD1C
2015-11-25 20:58 ` Andrey Repin
2015-11-25 21:34 ` Marco Atzeri
2015-11-25 22:53 ` Ken Brown
2015-11-26 1:28 ` Thomas Wolff
2015-11-25 21:03 ` 64bit cygwin 2.4.0-0.4 hangs when " Marco Atzeri
2015-11-26 20:20 ` Corinna Vinschen
2015-11-27 15:10 ` Corinna Vinschen
2015-11-27 16:04 ` Marco Atzeri
2015-11-28 19:02 ` Corinna Vinschen
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=56560930.70401@towo.net \
--to=towo@towo.net \
--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).