I'm not really sure but I think as long as chrony syncs with the NTP server that it's acceptable for our needs. That being said, could it be that both the NTP server (windows 2008R2) and the clients are on Vmware virtual machines? If is there a setting for the vmware VM or chrony to improve the dispersion? What's the downside of high dispersion?
Assaf Vainsencher Raytheon IIS 22110 Pacific Blvd, Dulles w. 571-250-3824 c. 571-294-8082 -----Original Message----- From: Bill Unruh [mailto:un...@physics.ubc.ca] Sent: Tuesday, November 28, 2017 9:14 PM To: chrony-users@chrony.tuxfamily.org Subject: [External] RE: Re: [chrony-users] Chrony 3.1 refuses to sync with ntp server On Tue, 28 Nov 2017, Assaf Vainsencher wrote: > Thank you. I confirmed that using maxdistance 16 fixed the issue we're > seeing. Looks like our root dispersion is just over 10 which is why we were > seeing the issue with the default setting in version 3.1. > Off topic, but I am really surprized by such a huge root dispersion. Are the ntp packets being delivered by sneakernet? Why would one want to use a timesource with such a huge dispersion/delay? -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org. -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
