From: Marco Atzeri <marco.atzeri@gmail.com>
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 12:04:00 -0000 [thread overview]
Message-ID: <56559566.7070808@gmail.com> (raw)
In-Reply-To: <56555DF4.9090804@towo.net>
On 25/11/2015 08:06, Thomas Wolff wrote:
> Am 24.11.2015 um 23:29 schrieb Marco Atzeri:
>>
>> ...
>> I assume it is an interaction with mintty.
> Many problems of that kind attributed to mintty are actually problems
> with cygwin or especially pty.
> Please test also with another terminal (xterm, rxvt, ...).
> Also some more details could be helpful as I cannot reproduce the issue
> (output of `type ping`, actual host pinged).
> ------
> Thomas
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.
Process Explorer or Task Manager are needed to kill the process.
Also kill -9 PID is ineffective
On the old cygwin.bat (aka windows cmd)
CTRL+C is effective
64 $ ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes
----2.2.2.2 PING Statistics----
2 packets transmitted, 0 packets received, 100.0% packet loss
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
next prev parent reply other threads:[~2015-11-25 11:03 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 [this message]
2015-11-25 19:04 ` Jim Reisert AD1C
2015-11-25 19:52 ` Thomas Wolff
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=56559566.7070808@gmail.com \
--to=marco.atzeri@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).