--On Friday, March 04, 2011 3:04 PM -0500 "Denniston, Todd A CIV
NAVSURFWARCENDIV Crane" wrote:
> Not if you are running ntp and it was able to sync, because ntpd
> activates a mode in the kernel that sets the hwclock every 11 minutes
> when ntp declares it got synced.
Thanks, this is the part
On Fri, Mar 4, 2011 at 3:04 PM, Denniston, Todd A CIV NAVSURFWARCENDIV
Crane wrote:
[snip]
> If your hwclock is off by a lot when it comes up I believe it is from
> one of the following:
> A) bad cmos battery.
> B) poor cmos clock
> C) confusing info in /etc/adjtime due to using both hwclock --adj
on 15:04 Fri 04 Mar, Denniston, Todd A CIV NAVSURFWARCENDIV Crane
(todd.dennis...@navy.mil) wrote:
>
> > -Original Message-
> > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> > Behalf Of Kenneth Porter
> > Sent: Friday, March 04, 2011 14:15
> > To: CentOS mailing
>yeah, definately, VM of any sort is a whole different beast, and
>no way NTP should be run in a virtualized environment.
The guests I run in KVM use ntp to keep their time accurate.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/ma
On Friday, March 04, 2011 04:05:43 pm m.r...@5-cent.us wrote:
> Excuse me? The last time I was following this closely, and I think the
> last time I looked, about a year ago, they said the opposite, that the
> guest, if running Linux, should use ntp.
>
> Right:
> NTP Recommendations
> Note: In all
On 03/04/11 12:59 PM, Lamar Owen wrote:
> On Friday, March 04, 2011 03:54:21 pm John R Pierce wrote:
>> just setup NTP and forget about it, and it will always work right,
>> unless your system is really badly broken, whereupon, it would be better
>> to fix it than to continue to hack around like th
Lamar Owen wrote:
> On Friday, March 04, 2011 03:54:21 pm John R Pierce wrote:
>> just setup NTP and forget about it, and it will always work right,
>> unless your system is really badly broken, whereupon, it would be better
>> to fix it than to continue to hack around like this.
>
> For the sake o
On 3/4/2011 3:59 PM, Lamar Owen wrote:
> On Friday, March 04, 2011 03:54:21 pm John R Pierce wrote:
>> just setup NTP and forget about it, and it will always work right,
>> unless your system is really badly broken, whereupon, it would be better
>> to fix it than to continue to hack around like thi
On Friday, March 04, 2011 03:54:21 pm John R Pierce wrote:
> just setup NTP and forget about it, and it will always work right,
> unless your system is really badly broken, whereupon, it would be better
> to fix it than to continue to hack around like this.
For the sake of the archives, VMware g
John R Pierce wrote:
> On 03/04/11 12:40 PM, Matt wrote:
>>
>> I add this to /etc/rc.local
>>
>> /usr/sbin/ntpdate us.pool.ntp.org
>>
>> Sets the clock on start up. Might run it by cron once a month or so
>> too.
>
> thats just the wrong way to go about it. if your clock is running fast,
> your c
On 03/04/11 12:40 PM, Matt wrote:
>
> I add this to /etc/rc.local
>
> /usr/sbin/ntpdate us.pool.ntp.org
>
> Sets the clock on start up. Might run it by cron once a month or so too.
thats just the wrong way to go about it. if your clock is running fast,
your cronjob will set it backwards, which
> Is there a package to do this?
>
> Normally the hardware clock is set during shutdown if one is running ntpd.
> But if a long-running server shuts down unexpectedly, this isn't done, and
> the hardware clock might be off by a lot when it comes back up. So setting
> it periodically from a cron job
>the hardware clock might be off by a lot when it comes back up.
If your server was set to use UTC time at install, the hardware clock will
always be wrong.
Check /etc/adjtime
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Kenneth Porter
> Sent: Friday, March 04, 2011 14:15
> To: CentOS mailing list
> Subject: [CentOS] Updating hardware clock from cron
>
> Is there a package to do this?
>
> Normally the
14 matches
Mail list logo
