From: Willy Tarreau <willy@w.ods.org>
To: jdow <jdow@earthlink.net>
Cc: Nick Warne <nick@linicks.net>, Wakko Warner <wakko@animx.eu.org>,
Bill Davidsen <davidsen@tmr.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OT] 1500 days uptime.
Date: Wed, 30 Nov 2005 06:31:08 +0100 [thread overview]
Message-ID: <20051130053108.GU11266@alpha.home.local> (raw)
In-Reply-To: <036c01c5f539$c54bd730$1225a8c0@kittycat>
On Tue, Nov 29, 2005 at 03:08:10PM -0800, jdow wrote:
> From: "Nick Warne" <nick@linicks.net>
(...)
> >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.
it may depend on what you do with it. I reached 1000 days with a
2.4.19pre5 plus a lot of patches a few years ago. However, it would
have been dangerous to leave this machine exposed because there were
so many local root exploits that the smallest vulnerability in any
installed service would have cause a disaster. But I also have some
machines running 2.4.22+some patches which have not been rebooted
since kernel upgrade, and which are used as front firewalls on a
big fat internet pipe, and they are still up and running normally.
So I can say that 2.4 was stable enough 2 years ago, and is even
more right now. Judging from the many people reporting years of
uptime (and from local experience), it seems that 2.4 reached such
a stability around 2.4.18.
> {o.o} Joanne Dow
Regards,
Willy
next prev parent reply other threads:[~2005-11-30 5:31 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 [this message]
2005-12-02 2:50 ` Bill Davidsen
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=20051130053108.GU11266@alpha.home.local \
--to=willy@w.ods.org \
--cc=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