News for hackers. Stuff that matters.
Re:SSH productivity tips by jff on Tuesday August 16, 2011 @01:47PM (#2892156)
If ssh servers and clients didn't use their own "keepalive" messages, you'd be able to do that anyway. TCP is supposed to be able to pick up right where it left off, so your ssh connections shouldn't die if you lose connection for a few minutes.
Re:SSH productivity tips by dedward on Wednesday August 17, 2011 @09:51AM (#2895336)
If you lose some packets for a few minutes, it shouldn't die,but there are a zillion real world situations where it can and WILL die....... and it's not an SSH problem, screen was useful for the same reason long before ssh.
Re:SSH productivity tips by shabble on Tuesday August 16, 2011 @01:56PM (#2892184)
man ssh_config:

TCPKeepAlive

Specifies whether the system should send TCP keepalive messages to the other side. If they are sent, death of the connection or crash of one of the machines will be properly noticed. However, this means that connections will die if the route is down temporarily, and some people find it annoying.

Re:SSH productivity tips by pyre on Tuesday August 16, 2011 @06:22PM (#2893142)
Turning off TCPKeepAlive also could mean that stale connections are killed. We have a router that kills connections that have been stale > 2 hours. I run my screen session on a single server and ssh to all other servers within that screen session. Without TCPKeepAlive, I would lose most of my session overnight (or after a string of meetings).