From owner-freebsd-current Sat Jun 5 17:17:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 7DA7114C40 for ; Sat, 5 Jun 1999 17:17:10 -0700 (PDT) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id UAA53918; Sat, 5 Jun 1999 20:13:56 -0400 (EDT) Date: Sat, 5 Jun 1999 20:13:56 -0400 (EDT) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Garrett Wollman Cc: Matthew Dillon , David Schwartz , Peter Wemm , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: RE: net.inet.tcp.always_keepalive on as default ? In-Reply-To: <199906052344.TAA19843@khavrinen.lcs.mit.edu> 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 On Sat, 5 Jun 1999, Garrett Wollman wrote: > < said: > > > FWIW, I think only a fool would want a computer to NOT drop dead connections. > > Any "connection" that doesn't respond after 8 $^&! tries spaced FAR apart does > > NOT deserve to stay. > > 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. > > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick > Brian Feldman _ __ ___ ____ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message