4 ms·

nice one, never seen that - always used ^D/exit

wyldfire 10y ago
Those are yet more graceful -- for when the shell is responsive. Use ~. in cases where for some reason you cannot get access to the terminal anymore but remote sshd is responsive.
- abstractbeliefs 10y ago
  iirc, enter-~-. isn't anything to do with the remote sshd. Instead, it escapes to the local ssh client (enter-~) that it should close (.). Which is really useful for if the remote sshd blew up, or, more commonly, your connection was broken.
- aji 10y ago
  ~. (and the other ~ commands) are handled locally, not by the remote sshd. I use it when my network cuts out or something and my ssh session is unrecoverably stuck
- 0x0 10y ago
  Actually the remote sshd does not need to be responsive, because "<cr>~." is interpreted by the local ssh client. Very convenient if the TCP connection is stuck. You can also type "<cr>~?" for a list of other commands supported by the local ssh client. Among other things, "<cr>~C" opens a command line interpreter on the client side of the ssh client, allowing you to add and remove TCP port forwarding without restarting the connection.
  - Tyr42 10y ago
    Ahg, I wish it let you scp files into your working directory too. That's be convenient.
    - thomashabets2 10y ago
      Long ago I sent a patch for uploading downloading using this escape sequence, using zmodem like how an old windows SSH client (I forget the name) used to allow uploading/downloading files. You log in, type "rz<enter>", and then use escape sequence to upload a file. (similar for downloading) The patch was rejected. Shame. It's very useful when hopping 6 steps to upload a file.[1] I can't find the patch now, but I'm considering rewriting it as a an `expect` script. My `expect` scripts tend to have trouble with SIGWINCH propagation though, so not optimal. Also you have to remember to wrap with the `expect` script at (and preferably only at) the one "jump" you want to send from/to with the final destination. [1] No, nothing illegal. Just that some networks mandate SSH jumpgates, and sometimes multi-level.
- russb 10y ago
  You can also layer the number of ~'s to skip over intermediary SSH sessions and send the escape to the proper one. \n~~. will escape the 2nd box you've SSH'd to, not the one it was originated from. Useful for escaping a screen'd SSH session that you might access through a jumphost.

Those are yet more graceful -- for when the shell is responsive. Use ~. in cases where for some reason you cannot get access to the terminal anymore but remote sshd is responsive.

abstractbeliefs 10y ago
iirc, enter-~-. isn't anything to do with the remote sshd. Instead, it escapes to the local ssh client (enter-~) that it should close (.). Which is really useful for if the remote sshd blew up, or, more commonly, your connection was broken.
aji 10y ago
~. (and the other ~ commands) are handled locally, not by the remote sshd. I use it when my network cuts out or something and my ssh session is unrecoverably stuck
0x0 10y ago
Actually the remote sshd does not need to be responsive, because "<cr>~." is interpreted by the local ssh client. Very convenient if the TCP connection is stuck. You can also type "<cr>~?" for a list of other commands supported by the local ssh client. Among other things, "<cr>~C" opens a command line interpreter on the client side of the ssh client, allowing you to add and remove TCP port forwarding without restarting the connection.
- Tyr42 10y ago
  Ahg, I wish it let you scp files into your working directory too. That's be convenient.
  - thomashabets2 10y ago
    Long ago I sent a patch for uploading downloading using this escape sequence, using zmodem like how an old windows SSH client (I forget the name) used to allow uploading/downloading files. You log in, type "rz<enter>", and then use escape sequence to upload a file. (similar for downloading) The patch was rejected. Shame. It's very useful when hopping 6 steps to upload a file.[1] I can't find the patch now, but I'm considering rewriting it as a an `expect` script. My `expect` scripts tend to have trouble with SIGWINCH propagation though, so not optimal. Also you have to remember to wrap with the `expect` script at (and preferably only at) the one "jump" you want to send from/to with the final destination. [1] No, nothing illegal. Just that some networks mandate SSH jumpgates, and sometimes multi-level.
russb 10y ago
You can also layer the number of ~'s to skip over intermediary SSH sessions and send the escape to the proper one. \n~~. will escape the 2nd box you've SSH'd to, not the one it was originated from. Useful for escaping a screen'd SSH session that you might access through a jumphost.