[ntp:questions] systems won't synchronize no matter what
kostecke at ntp.org
Thu Oct 28 19:55:46 UTC 2010
On 2010-10-28, unruh <unruh at wormhole.physics.ubc.ca> wrote:
> On 2010-10-28, Florin Andrei <florin at andrei.myip.org> wrote:
>> Here's the default ntp.conf that comes with CentOS 5, I assume all Red
>> Hat derivatives are very similar or identical:
>> # Permit time synchronization with our time source, but do not
>> # permit the source to query or modify the service on this system.
>> restrict default kod nomodify notrap nopeer noquery
>> restrict -6 default kod nomodify notrap nopeer noquery
>> # Permit all access over the loopback interface. This could
>> # be tightened as well, but to do so would effect some of
>> # the administrative functions.
>> restrict 127.0.0.1
>> restrict -6 ::1
> ?? Again, I would get rid of all of the restrict lines.
None of those restrict lines affect time service.
>> # Undisciplined Local Clock. This is a fake driver intended for backup
>> # and when no outside source of synchronized time is available.
>> server 127.127.1.0 # local clock
>> fudge 127.127.1.0 stratum 10
> Complete lunacy.
> It is NOT backup. It is not something that is useful for anything except
> to fool other machines into thinking you are synchronized when you are
Why not file a bug report in the offending OS' BTS? I doubt they follow
> [---=| TOFU protection by t-prot: 21 lines snipped |=---]
Steve Kostecke <kostecke at ntp.org>
NTP Public Services Project - http://support.ntp.org/
More information about the questions