Date: Tue, 1 Jun 1999 14:15:05 -0600 From: Nate Williams <nate@mt.sri.com> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: Matthew Hunt <mph@astro.caltech.edu>, kip@lyris.com, Nate Williams <nate@mt.sri.com>, current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <199906012015.OAA15519@mt.sri.com> In-Reply-To: <22394.928267922@critter.freebsd.dk> References: <19990601130331.A21176@wopr.caltech.edu> <22394.928267922@critter.freebsd.dk>
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 ? 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906012015.OAA15519>