Date: Tue, 28 May 2019 15:16:23 -0400 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: freebsd-questions@freebsd.org Subject: Re: ssh timeout question Message-ID: <44imtu8k54.fsf@be-well.ilk.org> In-Reply-To: <alpine.BSF.2.00.1905281433400.27739@bucksport.safeport.com> (Doug Denault's message of "Tue, 28 May 2019 14:42:22 -0400 (EDT)") References: <alpine.BSF.2.00.1905281433400.27739@bucksport.safeport.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Denault <doug@safeport.com> writes: > On Tue, 28 May 2019, RW via freebsd-questions wrote: > >> I doubt it's to do with timing out an idle connection since pine is >> polling for new mail ever 150s. > > Thank you all for comments and suggestions. It would not have occurred > to me to set the keep-alive value that small, I will try that. That is > a lot less irritating than my print a char script that mucks up > emails. In google I found someone suggesting setting "IPQoS > throughput" in $HOME/.ssh/config. I am going to try both when I next > go to a 100% fail location. I'll report back. > > I also find it strange that sitting in pine triggers the timeout but > sitting idle for days does not. I don't run into issues with this because my remote sessions tend to have an application running that updates an on-screen time display every minute. That's not why I do it, of course.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44imtu8k54.fsf>