Ask HN: moving beyond screen to persist SSH sessions?

Re:Ask HN: moving beyond screen to persist SSH sessions? by aolnerd on Tuesday February 10, 2009 @11:14AM (#475344)

When you start a local shell, you can generate some session identifier (export DURABLE_SESSION=$RANDOM) and put it in your environment. Then have your ssh client send it to the server with "-o SendEnv DURABLE_SESSION".

One question is when does sshd know when to ditch interrupted sessions.

[ Parent | on HN ]

Re:Ask HN: moving beyond screen to persist SSH sessions? by nuclear_eclipse on Tuesday February 10, 2009 @11:24AM (#475373)

You can always manually interrupt an SSH (or Telnet) session using the following key sequence:

    <Enter><Tilde><Period>

This sequence is caught by the SSH client to force a session disconnect.

[ Parent | on HN ]

Re:Ask HN: moving beyond screen to persist SSH sessions? by aolnerd on Tuesday February 10, 2009 @11:30AM (#475387)

You are of course correct, but that's not related to what I'm getting at.

My question raised the point that the server would not be able to tell the difference, after an interruption, between session state that the client will hope to resume and session state that should be discarded. That state would accumulate until some routine cleared it out.

[ Parent | on HN ]