public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Niels Kristian Jensen <nkj@internetgruppen.dk>
To: cygwin@cygwin.com
Subject: ssh cause mintty terminal not to close (tested on 4 cygwin installations)
Date: Thu, 02 Aug 2018 13:44:00 -0000	[thread overview]
Message-ID: <CAOxx+NJJJggH93wpULm8TrRO-M-M3FPdiu=UQ3QtRRwO-BYFSg@mail.gmail.com> (raw)

I've noticed a strange behavior of the standard Cygwin Terminal (mintty):

If I open a Cygwin Terminal (using the shortcut on the desktop installed by
Cygwin setup) and just press Ctrl-D, it writes "logout" and closes the
window as expected.

If I do the same, but give one command "ssh<enter>" first, the word
"logout" appear, the window goes black, but the window does not close (!) The
window can still be closed using the "X" in upper right corner.

If I replace the command with "ssh -V<enter>", the window closes as
expected when I press Ctrl-D.

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.

Tested versions:

Windows Server 2008 R2
OpenSSH_7.3p1, OpenSSL 1.0.2j  26 Sep 2016
mintty 2.7.0 (i686-pc-cygwin)

and

Windows 10
OpenSSH_7.6p1, OpenSSL 1.0.2m  2 Nov 2017
mintty 2.8.1 (i686-pc-cygwin)

Only commented lines appear in /etc/ssh_config , ~/.bashrc and
~/.bash_profile on both systems.

I would be glad if (some of) you could repeat this test on your system -
perhaps this behavior is due to some local problem on my systems.

Best regards,

Niels Kristian Jensen
Denmark

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

             reply	other threads:[~2018-08-02 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-02 13:44 Niels Kristian Jensen [this message]
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
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='CAOxx+NJJJggH93wpULm8TrRO-M-M3FPdiu=UQ3QtRRwO-BYFSg@mail.gmail.com' \
    --to=nkj@internetgruppen.dk \
    --cc=cygwin@cygwin.com \
    /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).