From owner-freebsd-chat Wed Jun 2 14:32:44 1999 Delivered-To: freebsd-chat@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 877FB14BEF for ; Wed, 2 Jun 1999 14:32:42 -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; Wed, 2 Jun 1999 14:32:40 -0700 From: "David Schwartz" To: "Matthew Hunt" , "Andre Oppermann" Cc: Subject: RE: net.inet.tcp.always_keepalive on as default ? Date: Wed, 2 Jun 1999 14:32:40 -0700 Message-ID: <000001bead3f$711c0840$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: <19990602140108.A47013@wopr.caltech.edu> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > That's how keepalives work. My understanding is that David Schwartz's > comment referred to application idle timeouts, not keepalives. Correct. Only the application can know whether the most logical means of dealing with the TCP connection is by a keepalive, data timeout, or other rule. Applications that have no data timeouts and do not enable keepalives are broken, period. I like the idea of having a ridiculously high keepalive time (like 1 week) even for connections that don't request them, and reverting to normal keepalive times for applications that do. That will help workaround broken applications. DS PS: Moved to chat since this is starting to look more like a holy war. ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message