Date: Tue, 28 May 2019 13:37:31 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-questions@freebsd.org Subject: Re: ssh timeout question Message-ID: <20190528133731.4f86f4b3@gumby.homeunix.com> In-Reply-To: <8daaed74-b18c-7b3d-12ff-baa76f894bfc@tridentusa.com> References: <alpine.BSF.2.00.1905271212240.61593@bucksport.safeport.com> <8daaed74-b18c-7b3d-12ff-baa76f894bfc@tridentusa.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 28 May 2019 07:37:36 -0400 John Johnstone wrote: > It's very common for HTTP connections between web browsers and > servers to also go idle before they are explicitly closed. This > results in the states being removed prematurely by the router. This > isn't noticed by the user though since the browser just opens a new > connection to the server. > > My guess would be that DHCP or number of active connections are not a > factor in your case. I doubt it's to do with timing out an idle connection since pine is polling for new mail ever 150s.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190528133731.4f86f4b3>