On 12/3/2011 12:00 PM, John Hardin wrote:
On Sat, 3 Dec 2011, Nightly Mass-Check Daemon wrote:
Sat Dec 3 06:10:01 UTC 2011
3 Dec 06:10:01 ntpdate[3368]: ntpdate 3-5.93e+sun 03/06/05 23:16:45
(1.4)
server 140.211.11.131, stratum 3, offset -10.438083, delay 0.21959
3 Dec 06:10:02 ntpdate[3368]: step time server 140.211.11.131 offset
-10.438083 sec
Cool, it works!
Apparently ntpd has not actually been set up or the clocks wouldn't
have drifted this far.
Would the clock in a zone drift if the host was NTP synced? Or would
that only help when the zone was restarted, and the zone itself also
needs ntpd installed and running to stay synced?
I'm going to guess this has more to do with the virtual nature. From
what I understand, it's supposed to sync from the "master" zone and that
has ntpd on it. but a 10 second drift is very large.
Should we open/re-open with infra?
