From owner-freebsd-arch Thu Aug 10 15:43:15 2000 Delivered-To: freebsd-arch@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id F16AC37B51F; Thu, 10 Aug 2000 15:43:13 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id PAA63523; Thu, 10 Aug 2000 15:43:14 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 10 Aug 2000 15:43:13 -0700 (PDT) From: Kris Kennaway To: Nik Clayton Cc: arch@freebsd.org Subject: Re: Turning tcp_extensions back on? In-Reply-To: <20000810141253.A2550@kilt.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 10 Aug 2000, Nik Clayton wrote: > [ Background -- NetCraft, the server statistics people, are about to start > producing reports where they figure out the uptime of the server's they're > talking to. I was talking to one of their engineers yesterday, and he > mentioned that FreeBSD doesn't work well with this, because most of the > deployed systems keep tcp_extensions turned off, and they use the RFC1323 > extensions to do the report. Obviously, if it's still an issue then we > should keep them turned off (and probably prepare some sort of text that > NetCraft can send out with the reports which explains why FreeBSD doesn't > figure very well in the report. Alternatively, if it's not a problem > any more then we should turn them on. ] Turning them on now won't help servers with 2 year uptimes unless they toggle the sysctl manually (not likely), or, uh, upgrade and reboot ;-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message