[OpenIndiana-discuss] ntpd not keeping time in sync

Roy Sigurd Karlsbakk roy at karlsbakk.net
Tue Jul 12 19:51:43 UTC 2011


> Sigh...
> 
> ntpdate -u 192.168.9.1
> 10 Jul 09:01:15 ntpdate[29929]: step time server 192.168.9.1 offset
> 3317.946738 sec

IIRC ntpd won't adjust the time if the difference is too big, measured between the system clock, inherited from the hardware clock, and the ntp servers. I've see this on VMs a few times on Linux - if the guest OS doesn't have a time source compatible, it'll usually drift a lot, possibly enough to make ntpd give up. But then, since you're running on iron (or silicon or something), adjusting the time on bootup with ntpdate should suffice :)

Vennlige hilsener / Best regards

roy
--
Roy Sigurd Karlsbakk
(+47) 97542685
roy at karlsbakk.net
http://blogg.karlsbakk.net/
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.



More information about the OpenIndiana-discuss mailing list