Date: Tue, 1 Jun 1999 13:03:31 -0700 From: Matthew Hunt <mph@astro.caltech.edu> To: kip@lyris.com Cc: Nate Williams <nate@mt.sri.com>, Poul-Henning Kamp <phk@FreeBSD.ORG>, current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990601130331.A21176@wopr.caltech.edu> In-Reply-To: <Pine.SOL.4.05.9906011233100.5802-100000@luna>; from kip@lyris.com on Tue, Jun 01, 1999 at 12:40:34PM -0700 References: <199906011851.MAA14756@mt.sri.com> <Pine.SOL.4.05.9906011233100.5802-100000@luna>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 01, 1999 at 12:40:34PM -0700, kip@lyris.com wrote: > declared dead. I think it somewhat silly to say that this is consuming a > lot of bandwidth. The average mail message (4k) is 4 packets, the average The other issue is that you don't necessarily want the TCP connection to close just because you lose connectivity for a few hours. If we send keepalives by default, might that not surprise users who don't expect it? I'm thinking of long-lived connections like telnet and ssh; if you're doing work over such a connection, it would be nice if the connection endured an outage while you're away sleeping, like it does without keepalives. -- Matthew Hunt <mph@astro.caltech.edu> * UNIX is a lever for the http://www.pobox.com/~mph/ * intellect. -J.R. Mashey 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?19990601130331.A21176>