2009/5/27 Andrew Gould <[email protected]>: > On Wed, May 27, 2009 at 8:45 AM, Chris Rees <[email protected]> wrote: >> >> 2009/5/27 Glen Barber <[email protected]>: >> > On Tue, May 26, 2009 at 11:23 PM, Polytropon <[email protected]> wrote: >> >> Maybe there's a way of patching the uptime utility that it adds >> >> the previous uptime of the system (since last shutdown) to the >> >> actual uptime. I know this denies everything uptime stands for, >> >> let's call it accumulated uptime. :-) >> >> >> > >> > I like that idea, actually.. Not for faking cumulative uptime. It'd >> > be kinda nice knowing how long a particular machine has been 'alive' >> > without looking through service tag records. >> > >> > -- >> > Glen Barber >> >> How about: >> >> [ch...@amnesiac]~% ls -l /etc/ssh/ssh_host_key.pub >> -rw-r--r-- 1 root wheel 324 Apr 15 2008 /etc/ssh/ssh_host_key.pub >> [ch...@amnesiac]~% >> >> I think I'd cry if I were to lose 553 days of uptime.... >> >> Chris > > You could write a script that sends uptime output and a start/stop flag to a > database when the system starts and stops. This wouldn't account for > improper shutdowns, although you could tell when a "stop" date/time was > missing. > > If you also documented the installation date/time of various components, > you could also track their lives separately. > > Andrew >
I use: http://www.uptimes-project.org/hosts/view/2288 Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[email protected]"
