Penguin

Differences between current version and previous revision of SSHNotes.

Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History

Newer page: version 81 Last edited on Sunday, April 3, 2011 2:22:11 am by AristotlePagaltzis
Older page: version 80 Last edited on Wednesday, January 28, 2009 9:48:13 am by AristotlePagaltzis Revert
@@ -171,9 +171,9 @@
  
 The possibilities are endless. In the standard case of using a slave [SSH] connection to some gateway, nothing stops you from using a <tt>~ProxyCommand</tt> in the alias configured for the gateway – so you can build an entire cascade of [SSH] tunneled connections from one gateway to the next. Of course eventually the onion of tunnels wrapped around the connection will push the latency up to and the throughput down to unworkable levels. 
  
  
-!!! Improving loss of connection detection / coping with flaky net links 
+!!! Improving the detection of lost connections / coping with flaky net links 
  
 Configure your [SSH] client to keep making sure it can still talk to the remote host if it hasn't received any data in a while. This is done by setting <tt>~ServerAliveInterval</tt> in your <tt>.ssh/config</tt> to how many seconds of silence the client should wait. The <tt>~ServerAliveCountMax</tt> directive defines how many attempts to get a reaction from the remote host may go unanswered before the [SSH] clients decides the connection has been lost. If you specify 5 seconds and 3 tries, a dead connection will be detected in 15 seconds. 
  
 The default values are 0 seconds, which means never, and 3 tries.