Date: Fri, 04 Jun 1999 22:21:04 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: dg@root.com Cc: "John R. LoVerso" <loverso@sitaranetworks.com>, current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <5663.928527664@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 04 Jun 1999 13:13:05 PDT." <199906042013.NAA29836@implode.root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199906042013.NAA29836@implode.root.com>, David Greenman writes: >>> I don't support increasing the default timeout. That would cause problems >>>for a lot of server systems that rely on the relatively short two hour default. >>>The best I think you could do would be to increase it to something like >>>12-24 hours as a default, but even that might be problematical. >>> Actually, I think we should leave it alone. I don't mind if people add an >>>rc.conf variable, however. >> >>First of all, our current default is not two hours, but to kill >>after 4 hours idle followed by no response for 20min: >> >> net.inet.tcp.keepidle: 14400 >> net.inet.tcp.keepintvl: 150 >> >>So anyone depending on two hours are screwed already. > > I believe the above numbers are in slowtimo ticks (500ms), so if you do >the math, you come up with 2 hours. Oops, you're right. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5663.928527664>