X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=0.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
Message-ID:	<4DDEA48A.9040806@ece.cmu.edu>
Date:	Thu, 26 May 2011 15:05:46 -0400
From:	Ryan Johnson <ryanjohn AT ece DOT cmu DOT edu>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: help developing a good problem report
References:	<BANLkTi=nofHYmFPvp6tV_b_DmG7RABOhsg AT mail DOT gmail DOT com>
In-Reply-To:	<BANLkTi=nofHYmFPvp6tV_b_DmG7RABOhsg@mail.gmail.com>
X-IsSubscribed:	yes
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

On 26/05/2011 1:10 PM, Rance Hall wrote:
> I've been noticing an issue with cygwin that I find annoying and would
> like to fix.
>
> Ive never submitted a cygwin problem report before so this is a first.
>
> My issue now is that I dont actually understand the problem well
> enough to give a good report.
>
> Here is what is happening:
>
> I'm using mintty to run ssh and connect to a remote box.
>
> I shutdown the remote box.
>
> ssh client exits with error
>
> Mintty locks up and does not accept user input (no keystrokes) till
> windows kills the session and it is restarted.
>
> Mintty does not lock up if I exit the remote ssh session properly
> without a remote shutdown.
>
> Always reproducible on win 7 64bit host.
>
> How can I determine if the problem is ssh or mintty?
I also encounter this problem, but I don't think it's a bug. I think it 
has to do with network timeouts in ssh: as far as mintty is concerned, 
ssh is active and it (ssh) should continue to control the terminal. 
Meanwhile, ssh is blocked trying to access a socket which it doesn't 
(yet) know has died, and is therefore not accepting user input.

If you kill ssh manually using the task manager, mintty becomes 
responsive again. Since I usually open a new mintty for each ssh 
connection, I usually go the lazy route and just close mintty with the 
big red 'X' in the corner ;)

You might try looking at the man page for ssh_config, and playing with 
ServerAliveCountMax and ServerAliveInterval, whose default values 
apparently give a 45 second timeout. There's also the unrelated 
TCPKeepAlive setting, but that's enabled by default and I don't know how 
long its timeout is (quite long, if my experience looking for AWOL 
network printers is any indication).

Ryan


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