Date: Wed, 27 May 2009 23:39:08 -0400 From: APseudoUtopia <apseudoutopia@gmail.com> To: vogelke+unix@pobox.com Cc: freebsd-questions@freebsd.org Subject: Re: Another uptime story Message-ID: <27ade5280905272039u1d116513seedfd86dee4ed75@mail.gmail.com> In-Reply-To: <20090527210037.315D9BEC7@kev.msw.wpafb.af.mil> References: <d356c5630905270702q31e06a0j31b48f138ed9b3b0@mail.gmail.com> <20090527210037.315D9BEC7@kev.msw.wpafb.af.mil>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 27, 2009 at 5:00 PM, Karl Vogel <vogelke+unix@pobox.com> wrote: >>> On Wed, 27 May 2009 09:02:08 -0500, >>> Andrew Gould <andrewlylegould@gmail.com> said: > > A> You could write a script that sends uptime output and a start/stop > A> flag to a database when the system starts and stops. =C2=A0This wouldn= 't > A> account for improper shutdowns, although you could tell when a "stop" > A> date/time was missing. > > =C2=A0 I have a script which runs fping on a bunch of servers and writes > =C2=A0 a timestamp for any host that answers. =C2=A0It's run every minute= from > =C2=A0 cron on our loghost. =C2=A0Another script watches the results and = sends > =C2=A0 me an IM if any of my boxes fails to respond for 3 minutes. > > =C2=A0 I can put up a tarball if anyone's interested. > I'd be interested in a set of scripts like that. I appreciate it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27ade5280905272039u1d116513seedfd86dee4ed75>