<story><title>How to kill an unresponsive ssh session</title><url>http://www.laszlo.nu/post/553591402/how-to-kill-an-unresponsive-ssh-session</url><text></text></story><parent_chain><item><author>oakenshield</author><text>It&apos;s like people don&apos;t know about man pages anymore. Google is the man page... only you may not get your answer on the first try.</text></item></parent_chain><comment><author>slmbrhrt</author><text>You can add Unix Manpages to your &quot;Subscribed Links&quot; in your Google preferences, and then you &lt;i&gt;will&lt;/i&gt; get your answer on the first try.</text></comment>
<story><title>How to kill an unresponsive ssh session</title><url>http://www.laszlo.nu/post/553591402/how-to-kill-an-unresponsive-ssh-session</url><text></text></story><parent_chain><item><author>oakenshield</author><text>It&apos;s like people don&apos;t know about man pages anymore. Google is the man page... only you may not get your answer on the first try.</text></item></parent_chain><comment><author>yason</author><text>They do but nobody wants to memorize everything off some man page. There are thousands and generally, man pages are considered references where you dig up one thing at a time.&lt;p&gt;Then there are man pages that are actually being studied with great care, such as bash. And even bash man page is notorious for containing an endless amount of information. You can read it several times and still you will bump into a blog post or HN comment that reveals some previously missed (but documented) bash feature.&lt;p&gt;Telnet conveniently prints &quot;Escape character is ^]&quot; and that&apos;s why everybody knows it. I must admit it probably never occurred to me that ssh must have some sort of escaping method as well.&lt;p&gt;Well, thanks to HN for that link anyway :)</text></comment>