Date: Tue, 16 Feb 1999 18:05:19 -0600 (CST) From: Jonathan Lemon <jlemon@americantv.com> To: advocacy@freebsd.org Subject: Re: FreeBSD robustness Message-ID: <199902170005.SAA29142@free.pcs> In-Reply-To: <local.mail.freebsd-advocacy/36C9F695.6FE5CE8A@softweyr.com> References: <local.mail.freebsd-advocacy/19990216134847.31204@right.PCS>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <local.mail.freebsd-advocacy/36C9F695.6FE5CE8A@softweyr.com> you write: >Jonathan Lemon wrote: >> >> 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. > >And stick a gargantuan UPS on it, so it'll live through the next halon- >dump test. Right? ;^) Actually, it's already on a huge UPS, and also has a diesel generator as a backup. However, the halon mechanism cuts _ALL_ power to the room. This means that it shuts down the UPS too. :-( -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902170005.SAA29142>