From owner-freebsd-current  Sat Jun  5 20:28:58 1999
Delivered-To: freebsd-current@freebsd.org
Received: from detlev.UUCP (tex-109.camalott.com [208.229.74.109])
	by hub.freebsd.org (Postfix) with ESMTP
	id E382114D35; Sat,  5 Jun 1999 20:28:50 -0700 (PDT)
	(envelope-from joelh@gnu.org)
Received: (from joelh@localhost)
	by detlev.UUCP (8.9.3/8.9.3) id WAA16899;
	Sat, 5 Jun 1999 22:28:57 -0500 (CDT)
	(envelope-from joelh)
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: <kip@lyris.com>, Julian Elischer <julian@whistle.com>,
	Nate Williams <nate@mt.sri.com>,
	Matthew Hunt <mph@astro.caltech.edu>,
	Poul-Henning Kamp <phk@FreeBSD.ORG>, current@FreeBSD.ORG
Subject: Re: net.inet.tcp.always_keepalive on as default ?
References: <Pine.SOL.4.05.9906011329260.6477-100000@luna> <xzpbtey4iby.fsf@localhost.ping.uio.no>
From: Joel Ray Holveck <joelh@gnu.org>
Date: 05 Jun 1999 22:28:56 -0500
In-Reply-To: Dag-Erling Smorgrav's message of "02 Jun 1999 19:34:41 +0200"
Message-ID: <86pv3ac8hz.fsf@detlev.UUCP>
Lines: 16
X-Mailer: Gnus v5.5/Emacs 20.3
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 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.

What's worst is probably that the bug doesn't affect operation.
Nobody I've talked to has ever seen a Windows 95 machine stay up for
over a week or so, let alone a month.

joelh

-- 
Joel Ray Holveck - joelh@gnu.org
   Fourth law of programming:
   Anything that can go wrong wi
sendmail: segmentation violation - core dumped


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message