Re: vmstat -s "boot time" Redhat Linux
From: Ethan Post <post.ethan_at_gmail.com>
Date: Fri, 13 Nov 2009 12:21:48 -0600
Message-ID: <357b48a90911131021u3a0dbab3nb9124bc016649875_at_mail.gmail.com>
OK, I get you now, I was thinking like uptime. I will have to check the uptime to see if it every changes, I will add some logging. We do have the clock thing figured out, that was an issue but no longer. The value definitely changed last night after a couple of days staying the same. I will have to check to see if it moved.
Date: Fri, 13 Nov 2009 12:21:48 -0600
Message-ID: <357b48a90911131021u3a0dbab3nb9124bc016649875_at_mail.gmail.com>
OK, I get you now, I was thinking like uptime. I will have to check the uptime to see if it every changes, I will add some logging. We do have the clock thing figured out, that was an issue but no longer. The value definitely changed last night after a couple of days staying the same. I will have to check to see if it moved.
On Fri, Nov 13, 2009 at 11:05 AM, Matthew Zito <mzito_at_gridapp.com> wrote:
>
> Well the boot time really shouldn't update if the machine hasn't rebooted
> in a physical environment - its not the duration since the boot, it's the
> specific boot time. In a virtual environment, you could be right, though
> theoretically in a non-paravirtualized environment it shouldn't be aware of
> moving to another host. Just a sanity check - the uptime doesn't change as
> part of that, does it?
>
> Matt
>
>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Nov 13 2009 - 12:21:48 CST