Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site wdl1.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!zehntel!dual!amdcad!fortune!wdl1!jbn
From: jbn@wdl1.UUCP
Newsgroups: net.unix-wizards
Subject: Re: Is 4.2BSD a failure?
Message-ID: <215@wdl1.UUCP>
Date: Mon, 21-Jan-85 21:24:20 EST
Article-I.D.: wdl1.215
Posted: Mon Jan 21 21:24:20 1985
Date-Received: Thu, 24-Jan-85 06:58:57 EST
Sender: notes@wdl1.UUCP
Organization: Ford Aerospace, Western Development Laboratories
Lines: 68
Nf-ID: #R:wdl1:17100032:wdl1:17100051:000:3020
Nf-From: wdl1!jbn    Jan 21 12:13:00 1985


      4.1BSD is a very stable system.  Below is our /usr/adm/shutdownlog for
the last six months or so, all on an original-release 4.1BSD system with
UNET networking.  No panics other than machine checks; most of the the
shutdowns shown below are for scheduled hardware or software service.
The machine is a 4MB VAX 11/780 with four CDC9766 disk spindles, supporting
about twenty users at a time.  (This is host FORD-WDL1.ARPA on the Internet.)
      Is anyone getting this level of stability with a 4.2BSD system?
Reports on ULTRIX would especially be appreciated.
      Perhaps there should be a newsgroup for exchanging uptime/downtime
data.

09:07  Mon Aug 13, 1984.  Reboot
09:28  Mon Aug 13, 1984.  Reboot
16:00  Fri Aug 17, 1984.  Shutdown: Going down for network fixing.  Back up in 1/2 hour (by jrb)
16:00  Fri Aug 17, 1984.  Halted.
16:19  Fri Aug 17, 1984.  Reboot
00:04  Sun Aug 26, 1984.  Reboot
16:00  Mon Aug 27, 1984.  Shutdown: system is going down for DEC repair (by root)
16:00  Mon Aug 27, 1984.  Halted.
16:56  Mon Aug 27, 1984.  Reboot
22:49  Mon Aug 27, 1984.  Shutdown: Reboot for network system (by root)
22:49  Mon Aug 27, 1984.  Halted.
23:10  Mon Aug 27, 1984.  Reboot
14:07  Thu Sep  6, 1984.  Reboot
09:18  Mon Sep 10, 1984.  Shutdown: DEC PM service (by root)
09:18  Mon Sep 10, 1984.  Halted.
10:39  Mon Sep 10, 1984.  Reboot
17:59  Mon Sep 10, 1984.  Shutdown: SYSTEM TROUBLE (by root)
17:59  Mon Sep 10, 1984.  Halted.
11:29  Tue Sep 11, 1984.  Shutdown: Going down for memory testitg (by root)
11:29  Tue Sep 11, 1984.  Halted.
12:39  Tue Sep 11, 1984.  Reboot
04:06  Wed Sep 19, 1984.  Reboot
12:56  Tue Sep 25, 1984.  Shutdown: (by root)
12:56  Tue Sep 25, 1984.  Halted.
13:14  Tue Sep 25, 1984.  Reboot
09:36  Sat Oct  6, 1984.  Shutdown: For System Maintenance (by root)
09:36  Sat Oct  6, 1984.  Halted.
00:50  Sun Mar 10, 1985.  Reboot
21:46  Sun Oct  7, 1984.  Shutdown: New Unet system (by root)
21:46  Sun Oct  7, 1984.  Halted.
22:04  Sun Oct  7, 1984.  Reboot
09:32  Mon Oct  8, 1984.  Shutdown: DEC PM (by root)
09:32  Mon Oct  8, 1984.  Halted.
10:01  Mon Oct  8, 1984.  Reboot
10:03  Mon Oct  8, 1984.  Shutdown: (by root)
10:03  Mon Oct  8, 1984.  Halted.
11:38  Mon Oct  8, 1984.  Reboot
06:51  Thu Oct 11, 1984.  Reboot
21:08  Fri Oct 19, 1984.  Shutdown: Tape drive hung (by root)
21:08  Fri Oct 19, 1984.  Halted.
21:27  Fri Oct 19, 1984.  Reboot after panic: mchk
08:41  Mon Oct 22, 1984.  Shutdown: DEC Maintenance (by root)
08:41  Mon Oct 22, 1984.  Halted.
02:33  Sun Mar 10, 1985.  Reboot after panic: mchk
09:05  Tue Nov 20, 1984.  Shutdown: (by root)
09:05  Tue Nov 20, 1984.  Halted.
12:22  Tue Nov 20, 1984.  Reboot after panic: mchk
13:36  Tue Nov 20, 1984.  Reboot
13:35  Wed Dec  5, 1984.  Reboot
02:29  Thu Dec  6, 1984.  Reboot
09:33  Mon Dec 10, 1984.  Reboot
11:59  Mon Dec 17, 1984.  Reboot after panic: mchk
11:21  Wed Jan 16, 1985.  Reboot
23:58  Thu Jan 17, 1985.  Shutdown: Reboot with larger system (by root)
23:58  Thu Jan 17, 1985.  Halted.