If you use an unstable time source, the clients will detect it and deem
the server unsuitable (marked as a false ticker.)
At that point all your clients drift on their own.
So, ya, it is important the the servers be stable. The clients can be a
bit unstable and the ntpd on them will fight the clock to keep it inline
with the server.
I like using the option "tinker panic 0" on all my client VMs so they
don't just give up.
On 04/04/16 18:58, Michael Ryder wrote:
Hello Jeremy
Admittedly, I don't know much about NTP other than it's purpose and some
of its abilities.
Without wanting to hijack this thread, I'm curious - are all of your NTP
clients, VMs themselves? If VMs are so bad at tracking time, then what
good are they for any reason? If an NTP client on a VM is able to track
time and keep it's guest OS in-sync, then why is an NTP server (in a VM)
any less accurate? Has anyone got a study they can reference?
Or...are your VMs part of a Windows AD domain? If so, you will probably
want to let your servers get their time sync from the domain
controllers, so as not to inflict Kerberos problems on yourself.
Or... are you sharing time for physical servers? If you have physical
servers, why not just install an NTP service onto one of them and be
done with it?
Mike
--
Mr. Flibble
King of the Potato People
http://www.linkedin.com/in/RobertLanning
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
