delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2010/08/18/07:11:01

X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_SV,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <AANLkTi=ypXQQ_0h9QKYjHP7FLFgrVLSFxaO5FjXip9JL@mail.gmail.com>
References: <AANLkTi=ypXQQ_0h9QKYjHP7FLFgrVLSFxaO5FjXip9JL AT mail DOT gmail DOT com>
Date: Wed, 18 Aug 2010 12:10:51 +0100
Message-ID: <AANLkTi=rRNCCunHjxUSE-3AeRx6tiSVxMup5vLzJpM5E@mail.gmail.com>
Subject: Re: mintty hangs after SSH disconnect
From: Andy Koppe <andy DOT koppe AT gmail DOT com>
To: cygwin AT cygwin DOT com
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 18 August 2010 09:51, Csaba Raduly wrote:
> The following scenario keeps happening more often than I like:
>
> I open a mintty console with a ssh:
> C:\cygwin17\bin\mintty.exe /bin/bash --login -c "/usr/bin/ssh -Y lablinux1"
>
> (time passes)
> I set the computer to sleep (the power button is reconfigured to sleep
> instead of shutdown).
>
> When I come back (usually the next day) and bring the computer back
> up, the SSH connection is lost:
> "Write error: connection reset by peer"
>
> This is understandable, considering the long time gap with no connection.
> The normal behavior is that after pressing Enter, the mintty window disappears.
>
> However, sometimes at this point mintty is consuming 100% CPU and has
> to be killed manually.

That's http://code.google.com/p/mintty/issues/detail?id=211, broken
since 0.8-beta1, reported and fixed in svn for 0.8.2 just last night.

Btw, the close button and Alt+F4 should still work inspite of the 100%
CPU. I guess I better also restore the behaviour where any keypress
closes the terminal if the pty has reported EOF.

Andy

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


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019