Timeline for Kill an unresponsive ssh session without closing the terminal
Current License: CC BY-SA 2.5
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 23, 2023 at 22:23 | comment | added | gcb |
@rsilva4 you probably have deadkeys. that is, you graphical interface have something that intercepts accents chars, hold them without forwarding to the application, until you press another letter to send the accented vowel. If you press the accent twice, it sends the accent alone. That's why you have to press ~~ to get ~. Ssh doesn't know about any of this.
|
|
| May 15, 2020 at 21:56 | comment | added | mazunki |
I was trying to ~^C, not understanding where to place the <kbd>Enter</kbd>, but ~. (as . apparently means to quit) followed by enter did the trick.
|
|
| Mar 11, 2013 at 21:10 | comment | added | rsilva4 |
In (at least) Portuguese keyboards double tap ~ and then .
|
|
| Jan 20, 2011 at 4:58 | history | edited | Steven D | CC BY-SA 2.5 |
added 3 characters in body; deleted 1 characters in body
|
| Oct 9, 2010 at 0:17 | vote | accept | Falmarri | ||
| Oct 9, 2010 at 0:04 | comment | added | Gilles 'SO- stop being evil' |
Actually this will work regardless of what is happening on the remote machine. What you've experienced is that ~ is only active immediately after you've pressed Enter (otherwise it would be too intrusive).
|
|
| Oct 8, 2010 at 23:34 | history | answered | Steven D | CC BY-SA 2.5 |