Xref: utzoo comp.realtime:738 comp.os.os9:1069
Path: utzoo!utgpu!watserv1!watmath!att!rutgers!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!decuac!shlump.nac.dec.com!alien.enet.dec.com!mcculley
From: mcculley@alien.enet.dec.com
Newsgroups: comp.realtime,comp.os.os9
Subject: Re: Time Problem on OS-9 Systems
Message-ID: <13391@shlump.nac.dec.com>
Date: 12 Jul 90 20:29:28 GMT
Sender: newsdaemon@shlump.nac.dec.com
Followup-To: comp.realtime
Organization: Digital Equipment Corporation
Lines: 23


In article <1990Jul5.190532.17243@cbnewsd.att.com>, knudsen@cbnewsd.att.com (michael.j.knudsen) writes...
> 
>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...?
>-- 

Guess it says something about various expectation settings that I'm more
surprised that four months is long enough to be noteworthy than I am that
hardware or software stayed up that long.  

I *-> expect <-* production systems (hardware and software) to be capable of
staying up indefinitely, unless I do something to cause them to be otherwise.

Why would anyone expect otherwise?

- Bruce McCulley
  Digital Equipment Corp.
  Corporate Software Engineering
  Nashua, NH USA