[RC5] Uptime and/or CPU time records?

Neil moebius at alt.net
Tue Jun 5 12:57:11 EDT 2001


Just checked the NT 4 server-
Client v2.8010-463-CTR-00071214: 3419 hours

No problems that I recall at the 49 day mark, but that has long left my
400k logfile.

-----Original Message-----
From: owner-rc5 at lists.distributed.net
[mailto:owner-rc5 at lists.distributed.net] On Behalf Of Brough, Adrian (IR
SOLUTIONS)
Sent: Tuesday, June 05, 2001 10:18 AM
To: 'rc5 at lists.distributed.net'
Subject: RE: [RC5] Uptime and/or CPU time records?


I hear rumers of the '49 day' bug in Windows, when a 32 bit free running
counter with a period of 1ms ticks over back to 0. Is this a myth or
does it actually exist. It is easy to work out the time of 49 days 17
hours 2 minutes and a few seconds.

Adrian
-----Original Message-----
From: Markus Landgren [mailto:marla252 at student.liu.se]
Sent: Tuesday, June 05, 2001 12:32 PM
To: rc5 at lists.distributed.net
Subject: Re: [RC5] Uptime and/or CPU time records?


I got 48 days of uptime out of it once. That might be considered
impressive since it was running under Windows 95.



At 19:16 2001-06-04 -0400, someone wrote:
>
>I was curious, does anyone have any dnet uptime or cpu usage records to

>share?  Ie. continuous uninterrupted execution times of the dnet 
>client.  I inadvertantly quit the cow the other day after logging about

>320 hours of CPU time, but I'm sure there are some die hards out there 
>that have
probably
>crunched for months at a time.
>
>
>PS.  I'm running dnet v2.8010 on Windows 2000
>
>-troy

--
To unsubscribe, send 'unsubscribe rc5' to
majordomo at lists.distributed.net rc5-digest subscribers replace rc5 with
rc5-digest
--
To unsubscribe, send 'unsubscribe rc5' to
majordomo at lists.distributed.net rc5-digest subscribers replace rc5 with
rc5-digest


--
To unsubscribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest



More information about the rc5 mailing list