Re: logout from interactive subshell

[Phil Pennock <phil.pennock@xxxxxxxxxxx>]

On 2006-10-13 at 08:17 -0400, Brian K. White wrote:
> rlogin, ssh, & telnet all support an escape character similar to classic cu.

I believe that Mike Stroyan already offered this one -- probably a mail
delay somewhere holding up parts of the thread though.

> 2) if you are connected from host to host to host, this breaks your closest 
> connection, not your furthest one.

> But if you only want to back out of your lest leg of the chain of 
> connections and not destroy the whole chain, I don't know how to do that 
> except by manually specifying a different escape character or sequence for 
> each new connection, so the the escape code for one connection gets ignored 
> and passed along as ordinary data by all the rest.

Repeat the escape.

If the second character is the escape character, then it's sent on as
one character, so the second ssh process sees it.  So assuming that it's
not been changed with EscapeChar/-e, ~. for the first, ~~. for the
second, ~~~. for the third, etc.  For each ssh, all that matters is that
the ~ be the first _seen_ character typed after a newline.

More safely, ~? to see which escape sequences are offered, so that you
can check it's working without logging out, or ~^Z to suspend the login.
Knowing that one, for chained sessions, is a major productivity boost.

Regards,
-Phil