On 31-12-08 00:18, Brian Foddy wrote: > I've been doing some network upgrades, and my ntpd was working pretty well > and > suddenly its acting very weird.
Perhaps, somewhere between your last restart of ntp (long ago) and this restart you modified the config with additional 'restrict' lines? If you then forgot to restart, you've never noticed that the 'new' ntp config is not good. > cat /etc/ntp.conf > <<...>> > server 127.127.1.0 # local clock > <<...>> > server ntp3.cs.wisc.edu #stratum 2 > server ntp.sycharlutheran.org #stratum 2 > server clock.nyc.he.net #stratum 1 > <<...>> > #restrict default ignore > restrict 127.0.0.1 > restrict default kod nomodify notrap nopeer noquery I just have these above two 'restrict' lines in my config. > restrict ntp.visi.com nomodify > restrict ntp3.cs.wisc.edu nomodify > restrict ntp.sycharlutheran.org nomodify > restrict ntp1.sjbcom.com nomodify > restrict clock.nyc.he.net nomodify I guess, here you explicitly state that you don't want your 'server' hosts to modify your time, so the only time source left for synchronization that is allowed to modify the time is the local clock (so, no external synchronization at all). I think, removing these lines solves your problem (but ntp config is sometimes not that straight forward and I have not checked it). Good luck, Arnold _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
