So we have a debate going on at my work place about what is causing this.
One of our linux servers hardware clock time goes way off if the ntpd servcie isnt running and keeping it in synced. When I mean way off I mean it falls about 8 hours off after about a week.
what do you guys think would cause this?
cmos battery?
bad firmware?
bad hardware?
Edit: oh and I forgot to mention that the server is only a year old.
On Tue, 2009-09-15 at 20:26 +0000, jaybott wrote:
> So we have a debate going on at my work place about what is causing
> this.
>
> One of our linux servers hardware clock time goes way off if the ntpd
> servcie isnt running and keeping it in synced. When I mean way off I
> mean it falls about 8 hours off after about a week.
>
> what do you guys think would cause this?
>
> cmos battery?
> bad firmware?
> bad hardware?
>
> Edit: oh and I forgot to mention that the server is only a year old.
Supply the FULL information about the platform… and we’ll be able to
guess better.
Are you sure it’s the hardware clock that skews? If so, then it’s
hardware related. However, 99.999% sure, the hardware clock has nothing
to do with this. In which case it’s just normal clock skew caused by a
plethora of reasons… depending on the FULL info…
I think we figured it out. Its running in vmware. I dont think you can have ntpd running if the host machine is set to sync with the vm.