Eduardo M KALINOWSKI wrote:
>Not really. uptime reports the amount of time elapsed since the
>system was booted, but I've noticed it is not paused for suspend
>and hibernation.
Yes:
$ uprecords
# Uptime | System Boot up
----------------------------+---------------------------------------------------
-> 1 113 days, 22:25:35 | Linux 3.2.0-4-amd64 Tue Dec 25 14:09:42 2012
----------------------------+---------------------------------------------------
NewRec 113 days, 22:25:34 | since Tue Dec 25 14:09:42 2012
up 113 days, 22:25:35 | since Tue Dec 25 14:09:42 2012
down 0 days, 00:00:00 | since Tue Dec 25 14:09:42 2012
%up 100.000 | since Tue Dec 25 14:09:42 2012
I must have rebooted it on Christmas day. It has definely not been switched on
for
113 days. My SSD reports 949 power on hours (=~ 1 month), and I'm fairly sure I
fitted it before Christmas.
On Wed, Apr 17, 2013 at 09:19:34PM -0500, Hugo Vanwoerkom wrote:
> Correct. Should that not be corrected? My desktop now says:
Corrected to what? "Uptime" means "time elapsed since the kernel was started"
and suspending or resuming doesn't really change that. It's also a rather old
and useless figure so I don't see the point in trying to make it more accurate.
For VMs, you could wonder whether context switches on a contended core should
be accounted for (and how)
Just checked my VPS:
13:40:10 up 401 days, 8:20, 9 users, load average: 0.01, 0.06, 0.08
Although I'm not proud of that, it's high time it was rebooted, most likely.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130418124403.GA26880@debian
