Date: 02 Jun 1999 19:34:41 +0200 From: Dag-Erling Smorgrav <des@flood.ping.uio.no> To: <kip@lyris.com> Cc: 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 ? Message-ID: <xzpbtey4iby.fsf@localhost.ping.uio.no> In-Reply-To: 's message of "Tue, 1 Jun 1999 13:30:37 -0700 (PDT)" References: <Pine.SOL.4.05.9906011329260.6477-100000@luna>
next in thread | previous in thread | raw e-mail | index | archive | help
<kip@lyris.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpbtey4iby.fsf>