From owner-freebsd-current  Tue Jun  1 13:11:57 1999
Delivered-To: freebsd-current@freebsd.org
Received: from gungnir.fnal.gov (gungnir.fnal.gov [131.225.80.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 1F09E14E9D; Tue,  1 Jun 1999 13:11:53 -0700 (PDT)
	(envelope-from crawdad@gungnir.fnal.gov)
Received: from gungnir.fnal.gov (localhost [127.0.0.1])
	by gungnir.fnal.gov (8.9.1/8.9.1) with ESMTP id PAA16774;
	Tue, 1 Jun 1999 15:11:49 -0500 (CDT)
Message-Id: <199906012011.PAA16774@gungnir.fnal.gov>
To: Poul-Henning Kamp <phk@FreeBSD.ORG>
Cc: current@FreeBSD.ORG
From: "Matt Crawford" <crawdad@fnal.gov>
Subject: Re: net.inet.tcp.always_keepalive on as default ? 
In-reply-to: Your message of Tue, 01 Jun 1999 20:41:00 +0200.
             <20883.928262460@critter.freebsd.dk> 
Date: Tue, 01 Jun 1999 15:11:49 -0500
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> ... and keep dynamic lines up when they should otherwise have been
> allowed to fall down.
> [...]
> The second argument falls on the same reasoning in my book, I don't
> know of any on-demand lines with a timeout longer than 10 minutes
> anyway.

But it will bring the line back *up*, to no useful purpose.

Always think very hard before messing with TCP.  And then don't.

			Matt Crawford


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message