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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=c0pBJ5IYQMAcY0XY
	sPed2eH/19WFUWuDBNp/+4d9m/VQUgeIv535DCgGZS5YNBwXH8nved/sXjEV0RDH
	hy9s4keLEmXVnhvu/AEhcI8NYWELWfUGmR7AdEwV5+qnxZBAbh1ZlbHC2UyijB4J
	rMWiyrpK+XDcmfSNskt3++S0ucM=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=f1Z63cdZL/2SwgEEnmGY9c
	sE8ys=; b=ntW8POVveFZ4XzbsA9evcV160/0vhiYiIxdNT3zU4bxboVXlul3wbN
	10x4ZY2Rg4NBFXwe8yk/2qMwyGRdSTcsVsId7ZM69wjQMqrR2nGI+pQ/bsBps2bR
	GFpTygrw8KRzJcMxLpu6TEBjflX73prvigLihjScieuonXQhwh2PE=
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: Yes, score=6.8 required=5.0 tests=AWL,BAYES_50,FOREIGN_BODY,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2
X-HELO: mout.kundenserver.de
Subject: Re: mintty hangs after exit
To: cygwin AT cygwin DOT com
References: <1778924762 DOT 20150822020530 AT yandex DOT ru> <28820-1440216321-185249 AT sneakemail DOT com> <55D7FB2D DOT 2020302 AT dwalin DOT fsnet DOT co DOT uk> <55D8006D DOT 4040409 AT towo DOT net> <193448468 DOT 20150822200332 AT yandex DOT ru>
From: Thomas Wolff <towo AT towo DOT net>
Message-ID: <55F68154.7050005@towo.net>
Date: Mon, 14 Sep 2015 10:12:04 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <193448468.20150822200332@yandex.ru>
Content-Type: text/plain; charset=windows-1252; format=flowed
X-UI-Out-Filterresults: notjunk:1;V01:K0:JhhpR9QCAwA=:QipltXOrm1B9e+tRoZWrd4 fXiAUu4NHXKTCVQgfh8FD0DBL5XFxGioBiDKbhCpCtFP+OanmFDoYIeUqJFRMQjEFkrtBHtEL oJXgNX8SKdkd57FejHAtSP7RKpGx4z/HLuexUeHC7dHshv5DbyZw7kj4tFQVdqLcJqPI3EFkv UOlRspXXamSGc4vJKhi91xA8lekUBp5sXHR4ZJ02edHb305+WbRZeA5pYBNEe+X2XbRPbAF6l 6lzksigXNld4yp7kEx/jLzdyTpbhPttQC57csF1FaukZD0G0sisrQch3tKsbyKZ5TDMu5y0ry 4h/HXqAt4BoFUug4G81C7m6qZy5IjwqsD8UJKXt6WyhFPMjzEJ1IFi3RI9TuoX9m7z4yVAyk1 FfOgs4DN2/RSDSCNzk54wKcc5FM8DDPRJKf6CLpLiULPdPyRtfAwBRMy5j9IKDKmCu09ZmDyh vtEIagkjxNCGeweD6iy7Z5jt1KxIqoQTlHm+s/JZLwrCgtkxxqF5tAY1UUNdDcpHEGhTAG73V MrV9iV7sMX+LcfWYxyoeoHVYOT3UUXWTkb0k72AOjI7zrfadKBlLmy7m7Dd2O9lPpdFAkjZkF UMvGXSnIHbgmOAfdiGEo7mzzLxiCfhVn3zteUwsd5uU4IEvWvhkbzQaaopHe1M9uwjxntq55T /vOIWI0ja1+ZGYeAiYv52GllzYgJUPFflDXRgGa+DCDLt906QN/kUV9TAKdPPnvDj5t9OXlaz pkg0zQiGB99Ca6vg9vVVq8Ft04FQSWQVYtsgOQ==
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t8E8CUWR025205

Sorry for some delay in responding to this again:

Am 22.08.2015 um 19:03 schrieb Andrey Repin:
> Greetings, Thomas Wolff!
>
>> Am 22.08.2015 um 06:31 schrieb Sam Edge:
>>> On 22/08/2015 05:05, John Hein wrote:
>>>> Andrey Repin wrote at 02:05 +0300 on Aug 22, 2015:
>>>>    > Just noticed a weird thing. Wonder if anyone can confirm or deny the issue.
>>>>    >
>>>>    > 1. Start mintty as `mintty.exe -` (i.e. login shell)
>>>>    > 2. Execute a command. S.a. "ssh anywhere"
>>>>    > 3. Exit all running apps. I.e. ^D out of all shells.
>>>>    > 4. mintty remains running.
>>>>    > There's no more child processes of it, nothing. It's just stuck around.
>>>>
>>>> ...
> ...
> And yes, it seems to only happen with OpenSSH.
> And pressing Enter in a stalled mintty window forces it to close.
I can reproduce this with the mintty option -h error or -o Hold=error
which I guess you have configured in .minttyrc.
Mintty does not terminate then if its child (usually the shell)
terminates with an error exit condition; in recent versions, it will
show a red notice about this.
You can easily try it by typing ^C in bash, then ^D, and mintty (with
hold error) will stay.
If you run ssh, and an error occurs in ssh (e.g. type ^C there as its
last action), that is apparently propagated back to the local shell.
Thomas

---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus


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