Date: Tue, 01 Jun 1999 22:12:02 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Matthew Hunt <mph@astro.caltech.edu> Cc: kip@lyris.com, Nate Williams <nate@mt.sri.com>, current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <22394.928267922@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 01 Jun 1999 13:03:31 PDT." <19990601130331.A21176@wopr.caltech.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22394.928267922>