Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.
Notice: I'm taking a break from blogging to focus on Atari Gamer . com, check it out!

NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ for more details.
It's a familiar sight, you have an SSH session open and have to step away from your computer for a few minutes. When you come back, your SSH session has been disconnected with an error like this...
Connection to myserver closed by remote host.
Connection to myserver closed.

Not cool SSH, not cool!

The error is due to an inactivity time out and is easily addressed. All you have to do is tell your SSH client to send a keep-alive packet every so often so that the SSH server will not disconnect you. To do that, edit your ~/.ssh/config file and make sure the following two lines are present:
KeepAlive yes
ServerAliveInterval 30

That's all there is to it. After making those changes the next time you connect via SSH you will not be disconnected due to inactivity.


Skip down to comments...
A quick disclaimer...

Although I put in a great effort into researching all the topics I cover, mistakes can happen. If you spot something out of place, please do let me know.

All content and opinions expressed on this Blog are my own and do not represent the opinions of my employer (Oracle). Use of any information contained in this blog post/article is subject to this disclaimer.
comments powered by Disqus
Other posts you may like...