public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Terminal output disappearing after SSH into cygwin
Date: Thu, 21 Jan 2021 16:13:59 +0100	[thread overview]
Message-ID: <d1aee930-43e0-e405-c094-2a4545ca09b5@gmail.com> (raw)
In-Reply-To: <644c7c45-b1a5-8c9f-8d6d-70b99a06c378@stefanist.com>

On 21.01.2021 14:08, Martyn B wrote:
> Hi list!
> 
> Usually after an ssh session, the lines in my terminal are persistant 
> after exiting the session. This is what I need.
> 
> But at the moment when I exit an ssh session into Cygwin, the terminal 
> gets cleared and all session information is lost.
> 
> How can I change this behavior? I need the commands and their output.
> 
> Server: Cygwin 3.1.4-1 on Windows 10 (1909), CYGWIN cygsshd
> Client: Ubuntu 20.04 / Gnome terminal, xterm

very simple:

ssh <your connection> |& tee /tmp/ssh.log


you can also use screen logging capability
https://stackpointer.io/unix/linux-ssh-session-logging/564/

  parent reply	other threads:[~2021-01-21 15:14 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
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 [this message]
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=d1aee930-43e0-e405-c094-2a4545ca09b5@gmail.com \
    --to=marco.atzeri@gmail.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).