From owner-freebsd-advocacy Tue Feb 16 11:53: 5 1999 Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26211 for ; Tue, 16 Feb 1999 11:53:02 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id NAA15365 for ; Tue, 16 Feb 1999 13:52:56 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id NAA03317; Tue, 16 Feb 1999 13:48:47 -0600 Message-ID: <19990216134847.31204@right.PCS> Date: Tue, 16 Feb 1999 13:48:47 -0600 From: Jonathan Lemon To: advocacy@freebsd.org Subject: FreeBSD robustness Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have to admit that I'm just a little bit disappointed. I have a machine which is acting as our corporate mailhub (all mail traffic passes through this machine), with the following stats: > uname -v FreeBSD 2.2-961014-SNAP #0: Tue Oct 15 01:27:25 1996 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC > uptime 1:43PM up 586 days, 5:52, 1 user, load averages: 1.11, 1.08, 1.02 The problem? We apparently are required (by fire department or insurance regulations) to test our halon system. This means that all power to the switch room will be cut for the duration of the test, and I have to shutdown the machine. I was hoping to get another 2 years out of it, barring hardware failures. Oh well. *sniff* At least it proves the robustness of the operating system, and I guess I'll take advantage of the downtime to load 3.1-RELEASE on it. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message