Date: Wed, 27 May 2009 16:53:52 -0400 (EDT) From: vogelke+unix@pobox.com (Karl Vogel) To: freebsd-questions@freebsd.org Subject: Re: Another uptime story Message-ID: <20090527205353.11DBEBEC7@kev.msw.wpafb.af.mil> In-Reply-To: <4A1CB002.9070904@ibctech.ca> (message from Steve Bertrand on Tue, 26 May 2009 23:14:10 -0400)
next in thread | previous in thread | raw e-mail | index | archive | help
>> On Tue, 26 May 2009 23:14:10 -0400,
>> Steve Bertrand <steve@ibctech.ca> said:
S> Just a little bit of sadness of having to 'down' it, given this uptime in
S> my relatively hostile environment. *sigh*
I'll match your sigh and add some curse-words. One of our fileservers:
date: Mon May 18 09:03:09 EDT 2009
uname: FreeBSD 4.9-RELEASE #0
uptime: 9:03AM up 732 days, 11:36, 0 users
Here's part of the output from "vmstat -s". I like the name lookups:
1644362297 cpu context switches
1093285479 device interrupts
1789304683 software interrupts
3124531993 traps
3752497578 system calls
2443779332 pages examined by the page daemon
1221349376 copy-on-write faults
3820203746 zero fill pages zeroed
1406714307 zero fill pages prezeroed
1893555896 total VM faults taken
3652052770 pages affected by fork()
2853118974 pages freed by exiting processes
-92074736 total name lookups
cache hits (449% pos + -1238% neg) system -1854% per-directory
deletions -18%, falsehits 0%, toolong 0%
Then our halfwit UPS decided to have a hissyfit and knock down this
system plus four others. Fortunately, our backup server stayed up:
date: Wed May 27 16:45:10 EDT 2009
uname: FreeBSD 6.1-RELEASE #0
uptime: 4:44PM up 595 days, 3:09, 1 user
--
Karl Vogel I don't speak for the USAF or my company
Si hoc legere scis nimium eruditionis habes
(Translation: If you can read this, you're overeducated)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090527205353.11DBEBEC7>