From owner-freebsd-current Tue Jun 1 13:37:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 3E3B1150AD for ; Tue, 1 Jun 1999 13:37:27 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA22054; Tue, 1 Jun 1999 13:30:32 -0700 (PDT) Date: Tue, 1 Jun 1999 13:30:31 -0700 (PDT) From: Julian Elischer To: David Schwartz Cc: Poul-Henning Kamp , Matthew Hunt , kip@lyris.com, Nate Williams , current@FreeBSD.ORG Subject: RE: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <000001beac6b$dc847920$021d85d1@whenever.youwant.to> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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