just to follow-up on my own thread, it turned out to be a xen issue.
issuing the command 'echo 1 > /proc/sys/xen/independent_wallclock' allowed
ntp to set the clock. not sure if this will have any negative effects but
at least my clock is right.
my dom0 has the correct time, anyone know if there's a better way to sync
time instead of relying on ntp in the domU?
jason
Jason Tower wrote:
got a dapper machine with the time too fast by 55 sec:
[EMAIL PROTECTED]:~# ntpdate -b pool.ntp.org
27 Jul 16:18:46 ntpdate[12420]: step time server 193.120.142.71 offset
\ -55.118258 sec
unfortunately that command is not fixing the time as it should, running
'date' still reports a time 55sec in the future. i tried ntpd but
doesn't work either:
Jul 27 15:55:16 murphy ntpd[11630]: time reset -55.023169 s
yet the clock is still off following the reset. note that this 55s is a
slow drift, it's only gaining a few seconds per day, but of course it
adds up.
wtf do i have to do to get the system clock set to the correct time?
jason
--
TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
