There may be more to this than meets the eye. Looking further into it,
it would appear that all of the xen guest servers are outside of the
defined limits for ntpd, which I read to be 128ms. Perhaps this is a
Xen problem.
Is there anyone on the list that is using Xen that could take the time
to do some research on their own systems.
Howard Lowndes wrote:
I have a number of servers, all of which match their system clocks to a
couple of central time sources that I run.
All, except 1, are within a couple of seconds of the time source. The
oddball is 13 seconds fast.
Even though its running ntpd and is seeing the time sources it still
won't sync. If I stop ntpd and run ntpdate manually then it
acknowledges that it is 13+ secs fast but still refuses to set the
system clock. (the doco says that ntpdate won't update if ntpd is running)
I should point out, though I don't see it as relevant, that this is a
Xen guest server and one of the reference clocks is the Xen host but the
other is independent.
Thoughts?
--
Howard.
LANNet Computing Associates - Your Linux people <http://lannetlinux.com>
When you want a computer system that works, just choose Linux;
When you want a computer system that works, just, choose Microsoft.
--
Flatter government, not fatter government; abolish the Australian states.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
