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:date:from:to:cc:subject:message-id
	:mime-version:content-type; q=dns; s=default; b=Uykr+xlzJbEg4Rqq
	i/CpZRYdn7zoasqd1WzCLgqrAfcSSq6aKkDZsZC3jIlegqeXM/L1hD0WBV7mmLTH
	V4aN/y9EdehHkrEZwlJczx77KRB63vwraaPnkd/+pIgK51j9kPK5v+Ggd4mCwLwV
	p+yx9F22swssvDRKOs5j8h343E4=
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:date:from:to:cc:subject:message-id
	:mime-version:content-type; s=default; bh=TVom/i4TetRrg7qiuWd6xO
	8qDdU=; b=JzmXfDA3gHZwJF6Gi7Z/Z1uVNS8sNQ+zaRdLtagoud7fD7mL0I3Hgv
	xylUtvTlwm58liDPzdYejsfTayxnlK3nEQ5LfFabMQAK7KP+WEAKhWmBsmT7pa1C
	C8kas5Jfkfeme05vRcjsSKAN65r3wt2OvCNWeMvQHRn3hcUZcn2Ao=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	plunk.org
Date:	Wed, 9 Oct 2013 18:19:15 -0400
From:	Don Hatch <hatch AT plunk DOT org>
To:	cygwin AT cygwin DOT com
Cc:	Don Hatch <hatch AT plunk DOT org>
Subject:	ssh takes forever to interrupt-- known problem?
Message-ID:	<20131009221915.GA6345@plunk.org>
MIME-Version:	1.0
User-Agent:	Mutt/1.5.21 (2010-09-15)
X-IsSubscribed:	yes

ssh'ing from a cygwin shell to a linux computer,
if I run an output-bound command
(e.g. "yes aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa")and I try to kill the command
using ctrl-c, it takes a long time, sometimes several minutes.
I'd love to get this fixed, as it's the one thing
that's preventing me from using cygwin/ssh effectively
as a remote terminal.

The problem occurs in the following situations:
    - cygwin ssh from windows to linux
    - cygwin ssh from windows to localhost
The problem does NOT occur in the following situations:
    - ssh from putty on windows to linux
    - ssh from linux to cygwin sshd on windows
    - ssh from linux to linux

So the problem seems to be unique to the cygwin ssh client.
Is this a known problem?
Any ideas why it would be like this for only this client,
and whether there are any inherent technical difficulties
that would make it hard to fix?

Note there is a post about this behavior on serverfault:
    http://serverfault.com/questions/32159/what-do-you-do-when-a-command-floods-your-terminal-with-too-much-output
although it doesn't mention it being specific to cygwin ssh.

Don


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

- Raw text -