This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: ssh cause mintty terminal not to close (tested on 4 cygwin installations)
- From: Brian Inglis <Brian dot Inglis at SystematicSw dot ab dot ca>
- To: cygwin at cygwin dot com
- Date: Fri, 3 Aug 2018 22:29:02 -0600
- Subject: Re: ssh cause mintty terminal not to close (tested on 4 cygwin installations)
- References: <CAOxx+NJJJggH93wpULm8TrRO-M-M3FPdiu=UQ3QtRRwO-BYFSg@mail.gmail.com> <1907135563.20180803000839@yandex.ru> <592e78b20f5c81db97104f235696e422@internetgruppen.dk>
- Reply-to: Brian dot Inglis at SystematicSw dot ab dot ca
On 2018-08-03 04:01, nkj@internetgruppen.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