lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200607311412.k6VECX1G004087@turing-police.cc.vt.edu>
Date:	Mon, 31 Jul 2006 10:12:33 -0400
From:	Valdis.Kletnieks@...edu
To:	Thomas Tuttle <thinkinginbinary@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Preserving uptime with kexec?

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...)



Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ