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

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
maybe we should fix our SERVER apps..
e.g. telnetd, sshd, etc. to have 1 week timeouts


On Tue, 1 Jun 1999, David Schwartz wrote:

> 
> 	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
> 



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?Pine.BSF.3.95.990601132954.13159J-100000>