From owner-freebsd-current Mon Jun 7 18:43:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 668CF1502B for ; Mon, 7 Jun 1999 18:42:28 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id VAA60319 for ; Mon, 7 Jun 1999 21:42:28 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <199906080142.VAA60319@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: net.inet.tcp.always_keepalive on as default ? References: <99Jun7.152505est.40335@border.alcanet.com.au> In-reply-to: Your message of "Mon, 07 Jun 1999 15:41:09 +1000." <99Jun7.152505est.40335@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Jun 1999 21:42:28 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There's also the the minor nit that there's no documentation. RTSL > may be OK for developers, but it's not really appropriate for end > users. This is aggravated by the timers being in 500ms units - phk > tripped over this recently. Before documenting it, how about we fix it's name to be more accurate to newcomers: net.inet.tcp.always_makedead, etc. There's no part of this (in many cases misguided) mechanism that keeps anything "alive." louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message