Date: Tue, 1 Jun 1999 14:27:56 -0600 From: Nate Williams <nate@mt.sri.com> To: David Malone <dwmalone@maths.tcd.ie> Cc: Nate Williams <nate@mt.sri.com>, Poul-Henning Kamp <phk@critter.freebsd.dk>, Matthew Hunt <mph@astro.caltech.edu>, kip@lyris.com, current@freebsd.org Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <199906012027.OAA15700@mt.sri.com> In-Reply-To: <19990601212045.A13137@bell.maths.tcd.ie> References: <19990601130331.A21176@wopr.caltech.edu> <22394.928267922@critter.freebsd.dk> <199906012015.OAA15519@mt.sri.com> <19990601212045.A13137@bell.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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 > > Surely that violates POLA? That upsets people who have keepalive > turned on already and find 1 week is way too long. For instance, > we use keepalive to get rid of stuck netscapes, and we'd probably > run out of swap or mbufs if it went up to a week. We just managed > by putting this in rc.local: > > sysctl -w net.inet.tcp.always_keepalive=1 As I understand it, it would always on, and 'one-week' would be the default. Old (traditional) programs that turned it on would be given the 'traditional' timeout of 1 hour. Or something like that. Off == 1 week KEEPALIVE ON == traditiona 1 hour KEEPALIVe. 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?199906012027.OAA15700>