Here is something I noticed which does not
make any difference in my use case, but.. FYI:
My host server is used to host guest distributions
- - mostly for software development
- - my host "sleeps" (suspend to ram) when I do
For the host:
wolf-c2q ~ # uptime
06:37:52 up 9 days, 14:11, 3 users, load average: 0.20, 0.06, 0.02
Which looks about correct (it is elapsed wall time) -
*including the wall time the system was asleep*
For the guests:
wolf-c2q ~ # vserver-stat
CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME
14156 2 8.4M 1.6M 0m00s42 0m00s49 1d08h43 deb-wolf
14158 2 6M 1.5M 4h16m10 24m52s83 1d08h43 gen2-32
Which looks a little bit strange -
even if the "asleep time" was deducted.
I **know** I have had them awake more than 32 hours in the
past 9 days (I don't know the exact time, but > 1d08h)
- - - -
Versions:
Kernel: 2.6.27.10-vs2.3.0.36.2
VS-API: 0x00020304
util-vserver: 0.30.215; Dec 17 2008, 10:37:16
Mike
Received on Thu Jun 4 12:51:02 2009