On 2014-05-13 15:03:48 +0200, Daniel Ortiz wrote: > dumb or not, I think that the ServerAliveInterval option solves the problem > mentioned by Jonathan without changing the way in which he does things.
I noticed in the past that ServerAliveInterval alone had a drawback: in case of temporary network problem (e.g. at least 15 minutes if ServerAliveInterval is set to 300), the SSH connection will be terminated. To avoid that, I suggest to also set ServerAliveCountMax to a large value. For instance, I have: ServerAliveInterval 300 ServerAliveCountMax 9999 > Of course there are other possibilities (such as the screen > command), but I think it is not exactly the answer that he was > looking for. Yes, this will solve most practical problems. For those who have ISP's / modem-routers which regularly break TCP connections, mosh (already mentioned), possibly combined with screen, will solve that. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) _______________________________________________ Gcc-cfarm-users mailing list Gcc-cfarm-users@gna.org https://mail.gna.org/listinfo/gcc-cfarm-users
