<div dir="ltr">If the problem is strictly related to timeouts there are 2 settings you should care about:<div><br></div><div>ClientAliveInterval and ClientAliveCountMax</div><div><br></div><div>My quick 30 second rundown:</div><div>ClientAliveInterval - how often the server sends a message to the client to ensure the session doesn't timeout</div><div>ClientAliveCountMax - number of times it sends a message before it decides that the client is a lazy bastard and times out the session</div><div><br></div><div>My settings (60 seconds and 4 hours):</div><div>ClientAliveInterval 60</div><div>ClientAliveCountMax 240</div><div><br></div><div>These are set in the sshd config on the server side, there are a couple of client side things you can do too, i like this because it doesn't require any of our engineers to set anything up on their side. We use this because we route some of our SSH connections through a network gateway that a 5 minute session timeout on anything that routes through it.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Dec 21, 2014 at 3:03 PM, Kevin Brandstatter <span dir="ltr"><<a href="mailto:icarusthecow@gmail.com" target="_blank">icarusthecow@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<a href="http://blog.hwarf.com/2009/06/howto-set-sshd-idle-timeout.html" target="_blank">http://blog.hwarf.com/2009/06/howto-set-sshd-idle-timeout.html</a><br>
<br>
Quick google search found that, which shows a parameter for the idle
timeout on the remote side.<br>
From the man page for sshd_config<br>
"""<br>
ClientAliveInterval<br>
Sets a timeout interval in seconds after which if no
data has been received<br>
from the client, sshd(8) will send a message through
the encrypted channel to<br>
request a response from the client. <b>The default is
0, indicating that these</b><b><br>
</b><b> messages will not be sent to the client</b>.
This option applies to protocol ver‐<br>
sion 2 only.<br>
"""<br>
I can only assume that means the server will do nothing to try and
keep the connection open.<br>
<br>
-Kevin<br>
<br>
<div>On 12/21/2014 02:59 PM, Freddy Martinez
wrote:<br>
</div>
<blockquote type="cite">
<p dir="ltr">The local sshd or the remote server?</p><div><div class="h5">
<div class="gmail_quote">On Dec 21, 2014 2:58 PM, "Kevin
Brandstatter" <<a href="mailto:icarusthecow@gmail.com" target="_blank">icarusthecow@gmail.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I use
terminator + tmux as well, and i've never really had a problem<br>
with ssh sessions other than the connections timing out<br>
if it sits idle for a while, but i've had that issue in just
about every<br>
setup. Might try looking into if theres an idle timeout
setting for sshd<br>
or something<br>
<br>
-Kevin<br>
<br>
On 12/21/2014 02:49 PM, Freddy Martinez wrote:<br>
> Hi folks,<br>
><br>
> I've been having a lot of issues lately with my SSH
sessions (I have<br>
> to maintain ~5 for 8+ hours a day with frequency having
to lock /<br>
> leave my work station). Here's my current setup. I use
Terminator and<br>
> have it split with 3-4 panes and just use SSH. I don't
use screen<br>
> because I find that it doesn't work great with
Terminator. Some of my<br>
> coworkers use tmux (you can launch it inside terminator)
but I dislike<br>
> the keybindings. The advantage of tmux is that is
supports screen-like<br>
> behavior but its actively supported. (screen isn't
maintained anymore<br>
> AFAIK).<br>
><br>
> What's your setup? Do anyone have a recommendation that
isn't tmux?<br>
> Ideally I'd like to use terminator + <something
else>.<br>
><br>
> Thanks,<br>
> Freddy M<br>
><br>
> _______________________________________________<br>
> discuss mailing list<br>
> <a href="mailto:discuss@lists.chicagolug.org" target="_blank">discuss@lists.chicagolug.org</a><br>
> <a href="http://lists.chicagolug.org/cgi-bin/mailman/listinfo/discuss" target="_blank">http://lists.chicagolug.org/cgi-bin/mailman/listinfo/discuss</a><br>
<br>
<br>
_______________________________________________<br>
discuss mailing list<br>
<a href="mailto:discuss@lists.chicagolug.org" target="_blank">discuss@lists.chicagolug.org</a><br>
<a href="http://lists.chicagolug.org/cgi-bin/mailman/listinfo/discuss" target="_blank">http://lists.chicagolug.org/cgi-bin/mailman/listinfo/discuss</a><br>
</blockquote>
</div>
</div></div></blockquote>
<br>
</div>
<br>_______________________________________________<br>
discuss mailing list<br>
<a href="mailto:discuss@lists.chicagolug.org">discuss@lists.chicagolug.org</a><br>
<a href="http://lists.chicagolug.org/cgi-bin/mailman/listinfo/discuss" target="_blank">http://lists.chicagolug.org/cgi-bin/mailman/listinfo/discuss</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Vytenis Silgalis</div>
</div>