From owner-freebsd-current Sat Jun 5 23:26:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D66E314C19 for ; Sat, 5 Jun 1999 23:26:30 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA17701; Sat, 5 Jun 1999 23:26:28 -0700 (PDT) (envelope-from dillon) Date: Sat, 5 Jun 1999 23:26:28 -0700 (PDT) From: Matthew Dillon Message-Id: <199906060626.XAA17701@apollo.backplane.com> To: Garrett Wollman Cc: Brian Feldman , current@FreeBSD.ORG Subject: Re: RE: net.inet.tcp.always_keepalive on as default ? References: <199906052344.TAA19843@khavrinen.lcs.mit.edu> <199906060057.UAA20103@khavrinen.lcs.mit.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :< said: : :>> If they are spaced too far apart, it is possible for perfectly :>> legitimate connections to get shot down as a result of external :>> periodicities. (Does somebody's router reset every day at 2:45? If :>> so, better hope no keepalives are scheduled for then!) : :> But remember that the idea is the keepalive would keep trying for a certain :> amount of time, and this would be finely configureable. : :This wouldn't help the poor sod whose connection gets shot down every :eight days while he's not there and doesn't know what hit him. If the poor sod hasn't touched his xterm for 8 days, he's either dead or he doesn't care if it goes away. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message