From owner-freebsd-current Wed Jun 2 10:34:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id C054114C30; Wed, 2 Jun 1999 10:34:50 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id TAA25583; Wed, 2 Jun 1999 19:34:42 +0200 (CEST) (envelope-from des) To: Cc: Julian Elischer , Nate Williams , Matthew Hunt , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: net.inet.tcp.always_keepalive on as default ? References: From: Dag-Erling Smorgrav Date: 02 Jun 1999 19:34:41 +0200 In-Reply-To: 's message of "Tue, 1 Jun 1999 13:30:37 -0700 (PDT)" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG writes: > Is it that long? I honestly don't think I have ever seen one stay up for a > week. Are you sure you did not mean 48 hours? I don't speak in jest. 49.7 days until an internal millisecond counter rolls around and crashes the machine. Microsoft have a patch out, but according to their web site, it's untested. I don't know what's worse; that Microsoft themselves can't keep Windows running for 50 days, or that they're incapable of manually bumping the counter to a value close to UINT_MAX and wait a few minutes for it to roll over. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message