From owner-freebsd-current Tue Jun 1 13:13:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 108A614E9D for ; Tue, 1 Jun 1999 13:13:37 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA22396; Tue, 1 Jun 1999 22:12:02 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Matthew Hunt Cc: kip@lyris.com, Nate Williams , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-reply-to: Your message of "Tue, 01 Jun 1999 13:03:31 PDT." <19990601130331.A21176@wopr.caltech.edu> Date: Tue, 01 Jun 1999 22:12:02 +0200 Message-ID: <22394.928267922@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mind you, this is only a problem because FreeBSD is to bloddy stable: I logged into a customers server a few days a go, it had been up for over a year, and had accumulated tons of ftpds from WIN* machines which had gotten a vulcan nerve pinch or a different IP#. (I'm sure windows NT servers doesn't have this problem at all) It doesn't have to be 2h timeout. I would be happy with a default of 24h, even one week would be OK with me. But infinity is too long for my taste. Can people live with a one week TCP keepalive as default ? -- 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