From owner-freebsd-questions@FreeBSD.ORG Wed May 27 14:10:40 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 177CD106567D for ; Wed, 27 May 2009 14:10:40 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: from mail-fx0-f159.google.com (mail-fx0-f159.google.com [209.85.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id 973948FC1A for ; Wed, 27 May 2009 14:10:39 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: by fxm3 with SMTP id 3so13078fxm.43 for ; Wed, 27 May 2009 07:10:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=ZSYEL9iWJA0CyY8NgBlWypMrvUvWArXMhK3gcBjd7Hc=; b=pDjrpXXdr0Ssu9/2vyO/ASlq4fDsy7FDxY2IyquwulzwzNMrcQ3M8ePn5FmcS96T3c EcQXWK+JOs0gZKUwvHweGqNZJj+odpiJ6TK5bYhwuYyWXXoj1kotn9oR+p0Afb/8+3T2 WILH0QIYhigwmrHnZrzmqq65amXhkeZhyLX08= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type:content-transfer-encoding; b=CibC+o6sPlx/Nit483AI72niqal1p9/HFD8x7Zaa9PTMIaddWfehO7DNj7IPWavkSZ A7pqWaTD6u5hdNRYaj8tYFQiQ4fUaUcurckU5zH1MC3CndOf76mHuvOo0O27YOY3m+JA zO0QE8qVR1VpcQ4M8dw5juxVIzLKyT31kmRy0= MIME-Version: 1.0 Received: by 10.204.60.133 with SMTP id p5mr12214bkh.143.1243433437168; Wed, 27 May 2009 07:10:37 -0700 (PDT) In-Reply-To: References: <4A1CB002.9070904@ibctech.ca> <20090527052335.7a71bfc6.freebsd@edvax.de> <4ad871310905262234s35857487xbf631bea45a018e@mail.gmail.com> From: Chris Rees Date: Wed, 27 May 2009 15:10:17 +0100 Message-ID: To: "freebsd-questions@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Another uptime story X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 May 2009 14:10:40 -0000 2009/5/27 Andrew Gould : > On Wed, May 27, 2009 at 8:45 AM, Chris Rees wrot= e: >> >> 2009/5/27 Glen Barber : >> > On Tue, May 26, 2009 at 11:23 PM, Polytropon 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. =A0It'd >> > be kinda nice knowing how long a particular machine has been 'alive' >> > without looking through service tag records. >> > >> > -- >> > Glen Barber >> >> How about: >> >> [chris@amnesiac]~% ls -l /etc/ssh/ssh_host_key.pub >> -rw-r--r-- =A01 root =A0wheel =A0324 Apr 15 =A02008 /etc/ssh/ssh_host_ke= y.pub >> [chris@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 t= o a > database when the system starts and stops.=A0 This wouldn't account for > improper shutdowns, although you could tell when a "stop" date/time was > missing. > > If you also=A0 documented the installation date/time of various component= s, > 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?