X-Spam-Check-By: sourceware.org
X-Matched-Lists: []
Message-ID: <380-220065331214032116@cantv.net>
Reply-To: rodmedina AT cantv DOT net
From: "Rodrigo Medina" <rodmedina AT cantv DOT net>
To: cygwin AT cygwin DOT com
Subject: Re: Ping does not receive CTRL-C
Date: Wed, 31 May 2006 17:40:32 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
X-Virus-Status: Clean
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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

On Wed, 31 May 2006,  Igor Peshansky  wrote:
>On Wed, 31 May 2006, Rodrigo Medina wrote:

>> Hi,
>>
>> I have found that, when a server does no respond, the ping program
>> is not interrupted by CTRL-C or CTRL-Z. In order to stop ping, one
>> has to open a new bash window and  kill the ping process from there.
>>
>> $ ping mail.ivic.ve
>> PING mail.ivic.ve (150.186.4.40): 56 data bytes
>>
>> The program stays there for ever.

>This was reported in <http://cygwin.com/ml/cygwin/2006-05/msg00571.html>
>and reported fixed in <http://cygwin.com/ml/cygwin/2006-05/msg00590.html>.
>FWIW, I can't reproduce this with the 20060529-15:56 snapshot.

It is not the same because inthis case the ping program is the one that is
distributed by cygwin. /bin/ping  the
native Windows ping  /cygdrive/c/WINDOWS/system32/ping works fine.

R. M.


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