From owner-freebsd-current Tue Jun 8 2: 5:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from turing.mathematik.uni-ulm.de (turing.mathematik.uni-ulm.de [134.60.166.1]) by hub.freebsd.org (Postfix) with SMTP id B877A14F30 for ; Tue, 8 Jun 1999 02:04:29 -0700 (PDT) (envelope-from kuebart@mathematik.uni-ulm.de) Received: by turing.mathematik.uni-ulm.de (5.x/UniUlm-2.0m) id AA05715; Tue, 8 Jun 1999 11:00:37 +0200 From: kuebart@mathematik.uni-ulm.de (Joachim Kuebart) Message-Id: <9906080900.AA05715@turing.mathematik.uni-ulm.de> Subject: Re: net.inet.tcp.always_keepalive on as default ? To: louie@TransSys.COM (Louis A. Mamakos) Date: Tue, 8 Jun 1999 11:00:37 +0200 (MET DST) Cc: current@FreeBSD.ORG In-Reply-To: <199906080142.VAA60319@whizzo.transsys.com> from "Louis A. Mamakos" at "Jun 7, 99 09:42:28 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Louis A. Mamakos wrote: > 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." I believe the rationale behind the nomenclature is to ``keep alive [connections]'', as opposed to keeping ``dead'' connections (whatever they are). cu Jo --------------------------------------------------------------------- PGP Key is at What am I doing here? God, these people drinking milk! But the clothes they wear look rather cool to me. Joachim Kuebart I wear the same -- what am I doing here? Ulm, Germany --- Banana Fishbones To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message