From owner-freebsd-current Tue Jun 1 13: 3:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id C46351503E; Tue, 1 Jun 1999 13:03:38 -0700 (PDT) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id NAA21559; Tue, 1 Jun 1999 13:03:31 -0700 (PDT) (envelope-from mph) Date: Tue, 1 Jun 1999 13:03:31 -0700 From: Matthew Hunt To: kip@lyris.com Cc: Nate Williams , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? Message-ID: <19990601130331.A21176@wopr.caltech.edu> References: <199906011851.MAA14756@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from kip@lyris.com on Tue, Jun 01, 1999 at 12:40:34PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 * 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