> I have checked into ntp/ntpd and found it to be broken too far for mere words. > It's avowed purpose is to find the One True UTC, I have an isolated gaggle of > machines on a private net that need to stay together regardless of how far that > 'together' drifts from WWV or some net-readable atomic clock. Given a gaggle > with no net connect to other machines outside the gaggle, ntp fails to perform, > and fails to explain why. It needs time source. Try putting this (taken from included example) to ntp.conf: ------------------------ # Undisciplined Local Clock. This is a fake driver intended for backup # and when no outside source of synchronized time is available. The # default stratum is usually 3, but in this case we elect to use stratum # 0. Since the server line does not have the prefer keyword, this driver # is never used for synchronization, unless no other other # synchronization source is available. In case the local host is # controlled by some external source, such as an external oscillator or # another protocol, the prefer keyword would cause the local host to # disregard all other synchronization sources, unless the kernel # modifications are in use and declare an unsynchronized condition. # server 127.127.1.0 # local clock fudge 127.127.1.0 stratum 10 ------------------------ > ntp's documentation frustrates and obfuscates. Unless there is an ntp HOWTO > for dummies, I've dumped ntp. Try reading " Notes on Configuring NTP and Setting up a NTP Subnet" from included docs. -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
