From owner-freebsd-current Fri Jun 4 10: 4: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 3F497153FE for ; Fri, 4 Jun 1999 10:03:59 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA08090; Fri, 4 Jun 1999 10:03:55 -0700 (PDT) (envelope-from dillon) Date: Fri, 4 Jun 1999 10:03:55 -0700 (PDT) From: Matthew Dillon Message-Id: <199906041703.KAA08090@apollo.backplane.com> To: David Malone Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <9906041725.aa11603@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think people just like to argue sometimes. The reality is different. For all you people complaining: Just turn them on and I guarentee you will not even notice the difference, except you will stop getting ( even the occassional ) stale internet server process. That is what keepalives were designed to deal with. Keepalives are not supposed to be a network watchdog, they are simply supposed to be a catch-all. So having per-socket adjustment is kind of silly. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message