This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Ctrl-C issues with 1.5.20-1
- From: "Auteria Wally Winzer Jr." <wwinzer at yahoo dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 3 Jul 2006 14:02:05 -0700 (PDT)
- Subject: Ctrl-C issues with 1.5.20-1
I noticed some very strange behavior with Ctrl-C. If I
ping a device on the local network I can Ctrl-C with
no problems, yet when I ping an outside device that's
not reachable Ctrl-C doesn't function whatsoever. This
wasn't an issue with 1.5.19-4:
$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=10
ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=11
ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=10
ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=10
ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=10
ms
----192.168.1.1 PING Statistics----
5 packets transmitted, 5 packets received, 0.0% packet
loss
round-trip (ms) min/avg/max/med = 10/10/11/10
wwinzer@wahleewhirl ~
$ ping www.yahoo.com
PING www.yahoo.akadns.net (209.73.186.238): 56 data
bytes
Ctrl-C is not functioning...
Regards,
Auteria
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/