From owner-freebsd-current Tue Jun 1 13:15:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (unknown [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id C85B014FD7 for ; Tue, 1 Jun 1999 13:15:14 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA20242; Tue, 1 Jun 1999 14:15:06 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA15519; Tue, 1 Jun 1999 14:15:05 -0600 Date: Tue, 1 Jun 1999 14:15:05 -0600 Message-Id: <199906012015.OAA15519@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Poul-Henning Kamp Cc: Matthew Hunt , kip@lyris.com, Nate Williams , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <22394.928267922@critter.freebsd.dk> References: <19990601130331.A21176@wopr.caltech.edu> <22394.928267922@critter.freebsd.dk> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid 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 ? Compromise. I like it. One week is certainly adequate for me. If I leave a link 'active' for longer than that w/out activity, I deserve to lose the link Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message