On 20Oct2015 23:50, Maurizio Marini <mau...@datalogica.com> wrote:
Until 3/4 days ago, I could leave all of them "hanging" for
DAYS, without typing anything at those prompts, and they'd
Maybe this parameter can helps?
ServerAliveInterval 60
I use this:
KeepAlive yes
TCPKeepAlive yes
ServerAliveCountMax 3
ServerAliveInterval 17
I tend to avoid 60 and other multiples/factors of a minute, just to skew things
a little. Not just in this, also in other intervals.
The upside is that intermediate stateful routers (oh, how we hates them) don't
decide your connection is dead so readily.
The downside is that if you have a network outage your shells may all die
because the ServerAliveInterval packets fail, and your client aborts.
Re mutt: similar behaviour because mutt supports IMAP's IDLE feature, so after
the initial frenzy of activity it enters a mode where it relies on the upstream
server to _annouce_ new messages, and is thus also a persistent idle TCP
connection.
Might I suggest that in addition to turning on ServerAliveInterval, you also
look at using tmux or screen on your remote servers if you're doing significant
stuff there - that way you can reconnect to those sessions if your ssh
connections abort.
Cheers,
Cameron Simpson <c...@zip.com.au>
The optimist proclaims that we live in the best of all possible worlds; the
pessimist fears this is true. - Branch Cabell, The Silver Stallion
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
