A lot of people don’t know that ssh has a number of escape sequences that can be run. I’ve often used the ~. to kill a stuck session but I recently discovered, by mistyping the aforementioned option, there is a number of other useful options too:
Supported escape sequences: ~. - terminate connection (and any multiplexed sessions) ~B - send a BREAK to the remote system ~C - open a command line ~R - Request rekey (SSH protocol 2 only) ~^Z - suspend ssh ~# - list forwarded connections ~& - background ssh (when waiting for connections to terminate) ~? - this message ~~ - send the escape character by typing it twice (Note that escapes are only recognized immediately after newline.)
RT @nullr0ute: SSH escape sequences: A lot of people don’t know that ssh has a number of escape sequences that can be run…. http://t.co/F…
@nullr0ute very handy, especially the one that increase/decrease the verbosity.
@nullr0ute Actually most people know about them as “Why the hell did my ssh session crash?” 🙂
Peter Robinson: SSH escape sequences http://t.co/UPfhqRTTvr