Xref: utzoo comp.realtime:730 comp.os.os9:1058
Path: utzoo!utgpu!watserv1!watmath!att!cbnewsd!knudsen
From: knudsen@cbnewsd.att.com (michael.j.knudsen)
Newsgroups: comp.realtime,comp.os.os9
Subject: Re: Time Problem on OS-9 Systems
Summary: Every OS should have this "Problem"
Message-ID: <1990Jul5.190532.17243@cbnewsd.att.com>
Date: 5 Jul 90 19:05:32 GMT
References: <2031@cernvax.UUCP> <2042@cernvax.UUCP>
Followup-To: comp.os.os9
Organization: AT&T Bell Laboratories
Lines: 15

In article <2042@cernvax.UUCP>, herbert@cernvax.UUCP (herbert walseth) writes:
>  If you intent to have your
> system continuously operational for more than four months, get hold
> of the new clock driver first!

A bug that bites only after 4 months of continuous operation
without a reboot?

Says something about OS9/K that such a problem should ever come up.
Also about the hardware used (except for the clock bug).
I wonder how many other OSes stay up that long...?
-- 

"Round and round the while() loop goes;
        Whether it stops," Turing says, "no one knows."