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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=Im3FVvEf0cvmf8wX
	vJeLm07jD/9nhsw3GSMiY3BOhlcEFDSB182oTtWnUQaZjuE5MEGRv6b0KGIpsAcw
	dnBqBiYk8cD95Yq2oT2tmbEnhf3irR6j+y5bD9XBSa4unSODVeTiq3qQ22w7mp1p
	eGfkoqHCEs3/pT9AdX0HZMlU3q0=
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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=cKnXxfsfLSEOTWD1Mjk8T6
	fCgfc=; b=ufIw3rCYu3Q9QB/81ZFGIRfSAk66U58WRY4b28URNW7w97k9spr08T
	vIQdOYISp5hXZbPwcwiPkiuL9aSx31MwzHrTD+Q+CBuSWXglfWBgdIUctsKpw7Qm
	fVIeOYCFvFDcftrNKGlfTGDPAwnPfDZ1yAkiUQ4RZo93yWkTTr7Qc=
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-Spam-SWARE-Status:	No, score=-1.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*Ad:D*ca, nkjinternetgruppendk, Hold, nkj AT internetgruppen DOT dk
X-HELO:	smtp-out-no.shaw.ca
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject:	Re: ssh cause mintty terminal not to close (tested on 4 cygwin installations)
To:	cygwin AT cygwin DOT com
References:	<CAOxx+NJJJggH93wpULm8TrRO-M-M3FPdiu=UQ3QtRRwO-BYFSg AT mail DOT gmail DOT com> <1907135563 DOT 20180803000839 AT yandex DOT ru> <592e78b20f5c81db97104f235696e422 AT internetgruppen DOT dk>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Openpgp:	preference=signencrypt
Message-ID:	<7b36297e-08c7-d049-fb1b-99ce1d83328a@SystematicSw.ab.ca>
Date:	Fri, 3 Aug 2018 22:29:02 -0600
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version:	1.0
In-Reply-To:	<592e78b20f5c81db97104f235696e422@internetgruppen.dk>
X-IsSubscribed:	yes

On 2018-08-03 04:01, nkj AT internetgruppen DOT dk wrote:
> On 2018-08-02 23:08, Andrey Repin wrote:
>> A long known issue.
>> mintty holds terminal open if last program finished with failure.
>> ssh somehow tripping this wire on occasion.
> OK.
>>> This may seem like a minor thing, but we have much trouble with Jenkins
>>> builds (started via Cygwin OpenSSH) which randomly hang forever - I wonder
>>>  if this could be a clue in this investigation.

If you are using ssh with mintty add "-h never":

-h, --hold[ |=]never|start|error|always
~/.minttyrc, /etc/minttyrc Hold=never|start|error|always

man mintty notes ssh returns 255 on connection errors

>> Try upgrading your mintty, also, if it's about automated building environment,
>> I don't see how's mintty can be involved.

QA/testers may prefer to run tests in a tty using script, or some test tool,
rather than redirection, in what could be a background shell.

> If the "non-closure" of mintty  is completely internal in mintty and not a
> handshake-mistake with the cygwin dll or the OS, then I agree. It seems to be
> the case, reading the link provided by Thomas Wolff.
-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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