E-Mail Sent to this address will be added to the BlackLists <Null@BlackList.Anitech-Systems.invalid> wrote:
> Anonymous wrote:> I decided to try to synchronize to my other machines > > in my network rather than the ntp pool I was using > > and after restarting the PC with the problem it is fine. > > I do not know what the problem was since the other boxes > > are still using the ntp pool and not having any issues > > so I will revert this PC to its original config to use > > the ntp pool again and see if it recurs. > > You don't happen to have the Undisciplined Local Clock Driver > 127.127.1.# configured? No, I don't. Here is the ntp.conf I have been using. I left the sample alone except for adding the pools for my zone. Thanks. # Sample /etc/ntp.conf: Configuration file for ntpd. # # 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 0.asia.pool.ntp.org server 1.asia.pool.ntp.org server 2.asia.pool.ntp.org server 3.asia.pool.ntp.org # # Drift file. Put this in a directory which the daemon can write to. # No symbolic links allowed, either, since the daemon updates the file # by creating a temporary in the same directory and then rename()'ing # it to the file. # driftfile /etc/ntp/drift multicastclient broadcastdelay 0.008 # # Keys file. If you want to diddle your server at run time, make a # keys file (mode 600 for sure) and define the key number to be # used for making requests. # PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote # systems might be able to reset your clock at will. # #keys /etc/ntp/keys #trustedkey 65535 #requestkey 65535 #controlkey 65535 # Don't serve time or stats to anyone else by default (more secure) restrict default noquery nomodify # Trust ourselves. :-) restrict 127.0.0.1 I didn't ever use the keys, maybe this could have been the problem? _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
