Re: vmstat -s "boot time" Redhat Linux

From: Jared Still <jkstill_at_gmail.com>
Date: Fri, 13 Nov 2009 09:18:37 -0800
Message-ID: <bf46380911130918g11d73719w8686d2cfb2f36d79_at_mail.gmail.com>

Never mind, that won't make any difference to 'boot time'.

I was thinking of 'uptime' for some reason.

Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com

On Fri, Nov 13, 2009 at 9:05 AM, Jared Still <jkstill_at_gmail.com> wrote:

> I'm no VMWare expert by any means, but if you don't have the
> VM tools installed in the VM, the clock will not be synced properly.
>
>
> Jared Still
> Certifiable Oracle DBA and Part Time Perl Evangelist
> Oracle Blog: http://jkstill.blogspot.com
> Home Page: http://jaredstill.com
>
>
>
>
> On Fri, Nov 13, 2009 at 9:02 AM, Ethan Post <post.ethan_at_gmail.com> wrote:
>
>> Maybe this is more VMWARE weirdness. The number is static for long periods
>> of time, and then after a few days goes up (perhaps when the image is
>> migrated to another server??).
>>
>> $ while ((1)); do
>> > vmstat -s | grep "boot time"
>> > sleep 600
>> > done
>> 1254804111 boot time
>> 1254804111 boot time
>>
>>
>>
>> On Fri, Nov 13, 2009 at 10:05 AM, Matthew Zito <mzito_at_gridapp.com> wrote:
>>
>>>
>>> That is the actual time in seconds since the epoch (unix time) that the
>>> machine was started. It's stored in /proc/stat, and vmstat just grabs the
>>> raw value and displays it with a slightly better label (it's btime in
>>> /proc/stat).
>>>
>>> So, in other words, take that unix time, convert it to a human-readable
>>> time, adn you've got when the machine was booted.
>>>
>>> Thanks,
>>> Matt
>>>
>>> --
>>> Matthew Zito
>>> Chief Scientist
>>> GridApp Systems
>>> P: 646-452-4090
>>> mzito_at_gridapp.com
>>> http://www.gridapp.com
>>>
>>>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Fri Nov 13 2009 - 11:18:37 CST