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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=KsZS/Kcnop2Yuygz7sBzEK1u0/tAQAfcq3KctTXibv5 /E8ZZ3ouorMPU/jOhYPO4OWi7lcJGp84MxXw36RDkT52Ifw5/JV9y5GdmPLiKNFv XoZisl61WUjJ7DAqAqTICX6Diwr4GHkaBoEe8EaGPmnLw/ICymuZ4yqXQmjXz4LM = 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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=kwiH5/L14slfS1FO4ASwXR6+qBI=; b=JJLYfAl5NbnHaq5P5 cXpD2qHTncQC/PzjlFuKP/xU7hhA1RoxtQZiZo7hmInQZALbUsuAoCP2hnE0ljX0 vZhnwueirV2/yMnZAx+bTx3LqOEK6eB9eaIaC78FDePzj//HlkC4MRtgOM1XYqLj M+DCz0UfK5RaIXnIl7VzaOemeM= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.0 required=5.0 tests=AWL,BAYES_05,FREEMAIL_FROM,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-qg0-f53.google.com X-Received: by 10.224.163.10 with SMTP id y10mr1402686qax.102.1396709411479; Sat, 05 Apr 2014 07:50:11 -0700 (PDT) Message-ID: <53401827.2030101@gmail.com> Date: Sat, 05 Apr 2014 10:50:15 -0400 From: Max Polk User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Ivan Todoroski , Cygwin list Subject: Re: 1.7.28: Ctrl-C not working reliably References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 4/4/2014 3:35 PM, Ivan Todoroski wrote: > On my machine, the Ctrl-C doesn't stop SSH from trying to ... I believe console applications may require I/O to/from stdin/stdout/stderr for Control-C (or even Control-S / Control-Q for flow control) to be noticed. In that period of time when there is "silence", no textual console output, no signal is even noticed, and the application happily continues what it is doing, totally ignoring you. I have seen this enough times to make me think it's a pattern, maybe even usual behavior. -- 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