From owner-freebsd-current Tue Jun 1 13:18:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 8C51515413 for ; Tue, 1 Jun 1999 13:18:09 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Tue, 1 Jun 1999 13:18:07 -0700 From: "David Schwartz" To: "Poul-Henning Kamp" , "Matthew Hunt" Cc: , "Nate Williams" , Subject: RE: net.inet.tcp.always_keepalive on as default ? Date: Tue, 1 Jun 1999 13:18:07 -0700 Message-ID: <000001beac6b$dc847920$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <22394.928267922@critter.freebsd.dk> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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