[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[firstname.lastname@example.org: FreeBSD robustness]
- To: SeaFUG <email@example.com>
- Subject: [firstname.lastname@example.org: FreeBSD robustness]
- From: Unfurl <email@example.com>
- Date: 16 Feb 1999 14:09:44 -0800
- Date: 16 Feb 1999 14:09:43 -0800
- Date: Tue, 16 Feb 1999 14:09:43 -0800
- Delivered-To: firstname.lastname@example.org
- Delivered-To: email@example.com
- Reply-To: firstname.lastname@example.org
- Sender: email@example.com
wow. Can you say 'uptime'?
----- Forwarded message from Jonathan Lemon <firstname.lastname@example.org> -----
Date: Tue, 16 Feb 1999 13:48:47 -0600
From: Jonathan Lemon <email@example.com>
Subject: FreeBSD robustness
X-Mailer: Mutt 0.61.1
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
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.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-advocacy" in the body of the message
----- End forwarded message -----
firstname.lastname@example.org - This is a munition. Fight Back!