public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Martyn B <mb@stefanist.com>
To: cygwin@cygwin.com
Subject: Re: Terminal output disappearing after SSH into cygwin
Date: Thu, 21 Jan 2021 15:45:28 +0100	[thread overview]
Message-ID: <e606608b-cab9-8e80-76b8-eb924f377787@stefanist.com> (raw)
In-Reply-To: <20210121222948.2e0044acb6d7475328f56ae2@nifty.ne.jp>

Takashi Yano via Cygwin wrote on 21.01.21 14:29:
> Takashi Yano via Cygwin <cygwin@cygwin.com> wrote:
>>
>> Please update cygwin to 3.1.7.
> 
> Sorry, I might misunderstand your problem.
> 
> Does your problem happen when you exit from ssh session to cygwin?
> If so, are you using ~/.bash_logout (for bash) or ~/.logout (for tcsh)?
> 

Thanks for asking.

Cygwin version is 3.1.7 now

This is exactly what happens:

-------------------------------------------------
     (1) Screen looks like this:
-------------------------------------------------

martyn@linuxbox:~$ echo local command 1
local command 1
martyn@linuxbox:~$ echo local command 2
local command 2
martyn@linuxbox:~$ ssh Winuser@<remote IP>

-------------------------------------------------
     hit RETURN
-------------------------------------------------
     (2) Screen looks like this:
-------------------------------------------------

martyn@linuxbox:~$ echo local command 1
local command 1
martyn@linuxbox:~$ echo local command 2
local command 2
martyn@linuxbox:~$ ssh Winuser@<remote IP>
Last login: Thu Jan 21 14:52:35 2021 from <local IP>

Winuser@WINDOWS-BOX ~
$ echo I want to keep this output
I want to keep this output

Winuser@WINDOWS-BOX ~
$ vim /home/Winuser/editing-testtext.txt

Winuser@WINDOWS-BOX ~
$ ls /home/Winuser/editing-testtext.txt
/home/Winuser/editing-testtext.txt

Winuser@WINDOWS-BOX ~
$ exit

-------------------------------------------------
     hit RETURN
-------------------------------------------------
     (3) Screen looks like this:
-------------------------------------------------

Connection to <remote IP> closed.
martyn@linuxbox:~$ echo all lines are gone
all lines are gone
martyn@linuxbox:~$

-------------------------------------------------
     ADDITIONAL INFORMATION
-------------------------------------------------
- same behavior if I use "exit" or "logout".
     "bash_logout" gives me "command not found"
- shell is /bin/bash on both sides
- the command "cygcheck -c Cygwin" clears the local lines from
     screen (1) immediately even _before_ exit


  reply	other threads:[~2021-01-21 14:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 13:08 Martyn B
2021-01-21 13:13 ` Takashi Yano
2021-01-21 13:29   ` Takashi Yano
2021-01-21 14:45     ` Martyn B [this message]
2021-01-21 17:28       ` Takashi Yano
2021-01-21 18:13         ` Ken Brown
2021-01-21 18:30           ` Takashi Yano
2021-01-21 19:06             ` matthew patton
2021-01-21 19:32             ` Ken Brown
2021-01-21 15:13 ` Marco Atzeri
2021-01-21 15:49   ` Martyn B
2021-01-21 16:02     ` matthew patton
2021-01-22  8:16       ` Brian Inglis
2021-01-22 11:10         ` Marco Atzeri
2021-01-22 13:18           ` (SOLVED) " Martyn B
2021-01-22 16:16           ` Thomas Wolff
2021-01-23 13:22             ` Martyn B
2021-01-23 14:50               ` Thomas Wolff
2021-01-22 15:27         ` Ken Brown

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=e606608b-cab9-8e80-76b8-eb924f377787@stefanist.com \
    --to=mb@stefanist.com \
    --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).