Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 1 Jun 1999 13:18:07 -0700
From:      "David Schwartz" <davids@webmaster.com>
To:        "Poul-Henning Kamp" <phk@critter.freebsd.dk>, "Matthew Hunt" <mph@astro.caltech.edu>
Cc:        <kip@lyris.com>, "Nate Williams" <nate@mt.sri.com>, <current@FreeBSD.ORG>
Subject:   RE: net.inet.tcp.always_keepalive on as default ? 
Message-ID:  <000001beac6b$dc847920$021d85d1@whenever.youwant.to>
In-Reply-To: <22394.928267922@critter.freebsd.dk>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

	Why not just fix the application programs that really want timeouts but
don't implement them?

	DS

> Mind you, this is only a problem because FreeBSD is to bloddy
> stable:  I logged into a customers server a few days a go, it had
> been up for over a year, and had accumulated tons of ftpds from
> WIN* machines which had gotten a vulcan nerve pinch or a different
> IP#.  (I'm sure windows NT servers doesn't have this problem at
> all)
>
> It doesn't have to be 2h timeout.  I would be happy with a default
> of 24h, even one week would be OK with me.
>
> But infinity is too long for my taste.
>
> Can people live with a one week TCP keepalive as default ?



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




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?000001beac6b$dc847920$021d85d1>