Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site mit-eddie.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!jg
From: jg@mit-eddie.UUCP (Jim Gettys)
Newsgroups: net.micro.att,net.unix-wizards
Subject: Re: instability in Berkeley versus AT&T releases
Message-ID: <4749@mit-eddie.UUCP>
Date: Sun, 21-Jul-85 09:13:21 EDT
Article-I.D.: mit-eddi.4749
Posted: Sun Jul 21 09:13:21 1985
Date-Received: Mon, 22-Jul-85 08:23:53 EDT
References: <2067@ucf-cs.UUCP> <363@cuae2.UUCP> <2423@sun.uucp> <406@petrus.UUCP> <2453@sun.uucp>
Reply-To: jg@mit-eddie.UUCP (Jim Gettys)
Organization: MIT, Cambridge, MA
Lines: 28
Xref: watmath net.micro.att:278 net.unix-wizards:13944

In article <2453@sun.uucp> guy@sun.uucp (Guy Harris) writes:
>...................................................... My
>machine is supplied by a "commercial vendor of 4.2BSD systems" (as is
>John's, I suspect :-) :-) :-)), and, well,
>
>	4:00pm  up 5 days,  2:33,  6 users,  load average: 0.23, 0.07, 0.00
>
>It's been up longer.  The only times it's crashed due to an OS bug are a few
>times when some pre-release software hung and it had to be rebooted (that
>problem hasn't recurred, and it wasn't the 4.2BSD base's fault) and once
>when it crashed due to some code I'd added (which, for the benefit of those
>of you who sneer at "lint", would have been reported by "lint"ing the
>kernel). ..................

I have seen an amusing bug in ruptime on our machines here (running a
"not commercially supported" version of 4.2).

mit-zeus    up  ??+17:42,     0 users,  load 0.01, 0.03, 0.03

This occurs if a machine has been up more than 99 days......
Several other machines on that local net had been up over 80 days, so
it was not a fluke.  Unfortunately, we had a power failure at 111 days.
Sigh....  I suppose we should all get up on our high horses and swear
at Berkeley for "buggy" software, but I for one am willing to forgive
them for this particular bug.

			Jim Gettys
			Project Athena