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:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=hkFjYRTbW/SoG78e
	A/9/j/pGowHacDStxkvTbeWZTawIMXRkayWEJwadPqvhLQr6ahNM+43cW8mwdEs0
	NwnP8WBMcNbhz1dsRI6RgLRAGutDOi3ECvTJgeQblkF26tpg1tZlGsVE5u/aykl5
	hQdHqi5z9Du8Y1a065UmO5zooNU=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-id: <5256164E.2010606@cygwin.com>
Date: Wed, 09 Oct 2013 22:51:58 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: ssh takes forever to interrupt-- known problem?
References: <20131009221915 DOT GA6345 AT plunk DOT org> <5255DAD2 DOT 5000707 AT cygwin DOT com> <20131009225852 DOT GA8151 AT plunk DOT org> <20131009232140 DOT GA9487 AT plunk DOT org> <5255E722 DOT 40008 AT cygwin DOT com> <20131010004449 DOT GA13071 AT plunk DOT org>
In-reply-to: <20131010004449.GA13071@plunk.org>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 10/9/2013 8:44 PM, Don Hatch wrote:
> On Wed, Oct 09, 2013 at 07:30:42PM -0400, Larry Hall (Cygwin) wrote:
>> ... Some of your packages are reported as empty, which isn't right.
>> See if you can make those complaints go away.
>
> Okay, I ran setup_x86.exe and uninstalled all packages
> that appeared as "empty" in the first cygcheck output.
> Ran cygcheck -s -r -v again, it showed a bunch of "Missing file:"
> in gcc-core and libserf1_0, so I uninstalled and reinstalled those
> two packages.
>
> Rebooted, ssh problem persists.
>
> New "cygcheck -s -r -v" output attached.

Thanks.  This looks better.

OK, I'm going to assume that 'sshd' was actually started when
you tried the latest rounds of tests.  If this wasn't the case, you have
another (probably non-Cygwin) SSH server running which is causing the
problem.  You'll need to shut that service down and start the Cygwin
one before trying again.

Beyond that, you could try invoking invoking 'yes' through 'strace' and
see if the output there gives you any clues.  You could also try cutting
down your path to eliminate potential interactions.  Lastly, you could
try adding "detect_bloda" to your Cygwin environment variable to see if
it points to some conflicting program/service:

<http://cygwin.com/cygwin-ug-net/using-cygwinenv.html#cygwinenv-implemented-options>

If those don't provide any clues, I'm out of ideas. :-(


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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