Hi,
I'd like to enquire about the following behaviour:
$ uptime && sudo hibernate && uptime
14:18:51 up 1 day, 4:12, 2 users, load average: 0.58, 3.30, 2.42
14:23:46 up 1 day, 4:17, 2 users, load average: 20.34, 7.74, 3.91
I.e. the system was suspended to disk for 5 minutes, but the value
reported by 'uptime' has increased by as much, as if it had actually
continued running during that time.
I'm using Linux 2.6.16 with the latest version of the Suspend 2 patch
(2.2.1), but Nigel its maintainer says that this isn't actually related
to his suspend code, essentially the same would happen using the swsusp
code currently in the kernel, and therefore we need to ask the kernel
time code people about this issue.
I've been using suspend2 for a while now, and until some point in the
past it used to be the case that uptime would stand still during
hibernation, i.e. only counting the time during which the system was
actually up and running. This seems like more meaningful and desirable
behaviour to me.
The way it is now, one can essentially "cheat": suspend a machine, put
it in the cupboard for a couple of weeks, resume it and claim a
respectable uptime, because the uptime value only reflects how long ago
the system was first booted up, with no regard to how much of that time
it has actually been running.
Would it be possible to get the old behaviour back?
Greetings,
--
jonathaN
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
