From owner-freebsd-current Fri Jun 4 13:19: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 83D7A14EEB for ; Fri, 4 Jun 1999 13:18:51 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id NAA29836; Fri, 4 Jun 1999 13:13:05 -0700 (PDT) Message-Id: <199906042013.NAA29836@implode.root.com> To: Poul-Henning Kamp Cc: "John R. LoVerso" , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Fri, 04 Jun 1999 21:27:57 +0200." <5419.928524477@critter.freebsd.dk> From: David Greenman Reply-To: dg@root.com Date: Fri, 04 Jun 1999 13:13:05 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> 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. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message