|
Toyonaka ContactMe help To Do Sell Buy Minoo Lorain Bicycle Lorain High School 1976 New Stuff Vancouver, BC ClassesResearchOJC infoMASLE References iPod Publications MediaDesignComputerSoftwarePoliticsTeaching and LearningLearning JapaneseMain.ReligionMusicFamilyFamily?SerendipityWiki ThoughtsPmWiki |
Computer /
OS Xterminalfrom http://www.macosxhints.com/article.php?story=20051219123255749 My ISP is very agressive about killing stalled connections. When no data has gone across an open connection, the ISP kills the connection. This killed ssh connections to remote machines constantly, and I found myself having to reconnect several times an hour if I was working on a machine remotely.
Fortunately, OSX 10.4 uses Open SSH? 3.8, which can send a packet at a regular interval to see if a server is alive. In my situation, this has the side benefit of actually keeping the connection open, since it resets whatever inactivity timer my ISP uses. Setting it up is pretty simple. Add the following to your .ssh/config file: Host * Server Alive Interval? 120 Server Alive Count Max? 3 This will send the server a message every 120 seconds, as per the Server Alive Interval? directive. The Server Alive Count Max? command tells it to kill the connection from the client end if the server hasn't responded after three messages (i.e. six minutes). So what this looks on my server is (see the stuff after host* the previous stuff, I'm not sure how it got there, but might have to do with my ssh hack: nairb:/Users/brian/.ssh root# more config Host s91158240.onlinehome.us User u35608008 Host * Server Alive Interval? 120 Server Alive Count Max? 3 |