Messages in this thread | | | Date | Mon, 31 Jul 2006 16:46:08 +0100 | From | "Nick Warne" <> | Subject | Re: Preserving uptime with kexec? |
| |
Speaking of which, I have submitted a claim to Guiness Book of Records for my uptime on a lowly 486 box that serves my webpages (via NFS) as a 'home user' (I am sure business classed machines do better with UPS etc.). I have posted here twice when it hit 1000 days and then 1500 days:
[nick@486Linux nick]$ uname -a Linux 486Linux 2.2.13-7mdk #1 Wed Sep 15 18:02:18 CEST 1999 i486 unknown
[nick@486Linux nick]$ last -xf /var/run/utmp runlevel runlevel (to lvl 3) Sun Oct 14 16:07 - 16:42 (1751+00:34)
The claim has been accepted, and is now in evaluation... so I dunno what happens next until I hear from them (or how it can be verified unless someone pops along and I telnet into the box for them).
Nick
On 31/07/06, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote: > On Mon, 31 Jul 2006 08:59:13 EDT, Thomas Tuttle said: > > Like many people, I like to brag about how great my uptime is. But like > > many other people, I like to keep my kernel up-to-date with the latest > > and greatest from kernel.org. I recently discovered the magic of kexec, > > which allows me to switch kernels without rebooting for real. > > Unfortunately, kexec resets my uptime when it runs. > > The reset of uptime is probably a Good Thing. Consider the case of > a kernel memory leak - you look in /proc/meminfo and find that you've > managed > to lose 64 meg of memory to the leak. Where you start looking for the > leak will depend on whether it's 64 meg lost across 4 weeks since the > last boot, or the 30 minutes since the last boot. > > (Speaking as somebody who's run into both classes of leaks...) > > > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |