From: Bill Davidsen <davidsen@tmr.com>
To: jdow <jdow@earthlink.net>
Cc: Nick Warne <nick@linicks.net>, Wakko Warner <wakko@animx.eu.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OT] 1500 days uptime.
Date: Thu, 01 Dec 2005 21:50:25 -0500 [thread overview]
Message-ID: <438FB671.9060701@tmr.com> (raw)
In-Reply-To: <036c01c5f539$c54bd730$1225a8c0@kittycat>
jdow wrote:
> From: "Nick Warne" <nick@linicks.net>
>
>> On Tuesday 29 November 2005 00:31, Wakko Warner wrote:
>>
>>> Bill Davidsen wrote:
>>> > Nick Warne wrote:
>>> > >Hi all,
>>> > >
>>> > >BrrrrrrrrrrrrBrrrr
>>> > >
>>> > >That was me blowing my own trumpet again :-)
>>> > >
>>> > >Re:
>>> > >http://www.ussg.iu.edu/hypermail/linux/kernel/0407.1/0651.html
>>> > >
>>> > >Now just hit 1500 days:
>>> > >
>>> > >-
>>> > >[nick@486Linux nick]$ last -xf /var/run/utmp runlevel
>>> > >runlevel (to lvl 3) Sun Oct 14 16:07 - 21:41
>>> > >(1502+06:34)
>>> > >
>>> > >utmp begins Sun Oct 14 16:07:40 2001
>>> > >-
>>> > >
>>> > >Utterly remarkable - the box gets no maintenance at all.
>>> >
>>> > But it clearly gets a very reliable flavor of electricity...
>>> >
>>> > >I would love to know how much data it has delivered, but alas, in
>>> 2001 I
>>> > >wasn't up-to-speed with that sort of thing :-)
>>> >
>>> > We got one to 1460 or so, then got BSOD on the controller which
>>> switches
>>> > from the UPS to the diesel when they get up to speed, dropped
>>> power on
>>> > the whole data center (at work).
>>> >
>>> > I think you have the record, though.
>>>
>>> I'm not sure about that one. =)
>>
>>
>> No, I wasn't even thinking that - just reporting what a wonderful job
>> it all is - and yes, power supply here in Pompey UK is good (but we
>> do pay thru' the nose for everything in the UK). The last time I
>> _did_ reboot that machine was when my kettle lead shorted out and
>> blew the fuses to my flats 240v supply ring main.
>>
>> According to the Linux counter site, there are more higher (my
>> machine is 3rd in the list):
>>
>> http://counter.li.org/reports/uptimestats.php
>
>
> There is an interesting point here that is worth noting. I don't think I
> would BEGIN to try this with a 2.6 based kernel. And I am not sure it is
> doable yet with a 2.4 kernel if the machine is to be exposed to the wild.
>
> {o.o} Joanne Dow
>
I got 0.99.4 to stay up 16 weeks ;-)
And the old GE/Honeywell 600 crashed due to rollover at 35 days, and we
hit the bug first three years after it was coded. Hardware is better!
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
prev parent reply other threads:[~2005-12-02 2:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 21:47 [OT] 1500 days uptime Nick Warne
[not found] ` <200511242332.13556.Norbert@hipersonik.com>
2005-11-24 22:35 ` Nick Warne
[not found] ` <438641F8.4030709@st-andrews.ac.uk>
2005-11-24 22:58 ` Nick Warne
2005-11-24 23:05 ` Norbert van Nobelen
2005-11-25 10:09 ` Tim Schmielau
2005-11-25 2:04 ` J. Scott Kasten
2005-11-28 22:51 ` Bill Davidsen
2005-11-29 0:31 ` Wakko Warner
2005-11-29 22:26 ` Nick Warne
2005-11-29 23:02 ` Wakko Warner
2005-11-29 22:48 ` Nick Warne
2005-11-30 1:16 ` Wakko Warner
2005-11-29 23:08 ` jdow
2005-11-30 5:31 ` Willy Tarreau
2005-12-02 2:50 ` Bill Davidsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=438FB671.9060701@tmr.com \
--to=davidsen@tmr.com \
--cc=jdow@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
--cc=wakko@animx.eu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox