From: Andrey Repin <anrdaemon@yandex.ru>
To: Niels Kristian Jensen <nkj@internetgruppen.dk>, cygwin@cygwin.com
Subject: Re: ssh cause mintty terminal not to close (tested on 4 cygwin installations)
Date: Fri, 03 Aug 2018 22:35:00 -0000 [thread overview]
Message-ID: <1609697605.20180804012442@yandex.ru> (raw)
In-Reply-To: <592e78b20f5c81db97104f235696e422@internetgruppen.dk>
Greetings, Niels Kristian Jensen!
>>> 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.
>>
> (cut)
>>
>> Try upgrading your mintty, also, if it's about automated building
>> environment,
>> I don't see how's mintty can be involved.
> 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.
What I wanted to say is that I don't understand, why do you use mintty in this
specific case.
Can you provide a bit more background? Do you use it exclusively to call SSH
to some remote host?
P.S.
If it wouldn't be a big thing to ask of you, could you please configure your
email client to properly fill your "from" name?
I'm not very comfortable talking to email :)
--
With best regards,
Andrey Repin
Saturday, August 4, 2018 1:21:09
Sorry for my terrible english...
--
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
next prev parent reply other threads:[~2018-08-03 22:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 13:44 Niels Kristian Jensen
2018-08-02 14:36 ` cyg Simple
2018-08-02 21:07 ` Thomas Wolff
2018-08-02 21:20 ` Andrey Repin
2018-08-03 10:02 ` nkj
2018-08-03 22:35 ` Andrey Repin [this message]
2018-08-06 10:31 ` Niels Kristian "Ænkå" Jensen
2018-08-03 23:43 ` cyg Simple
2018-08-04 4:29 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1609697605.20180804012442@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=nkj@internetgruppen.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).