John Pettitt wrote on 26-2-2008 7:56: > Evandro Menezes wrote: >> Can someone shoot this server, please: >> http://www.pool.ntp.org/scores/63.240.161.99 ? > wow - that's quite a slope on that line.
Interesting... That server is not open for ntpq queries, but it looks as if it's not syncing to anything except itself. What we see here is exactly the reason that we shouldn't use that LOCAL pseudo refclock driver. Normally, ntpd will stop service after it has lost sync to all servers for some time. The LOCAL clock driver is there to prevent that from happening, but it shouldn't be used unless the local oscillator is disciplined by Cs or Rb (or an oven at the very least). This may be a nice opportunity for pool operators to review their ntp.conf. Get rid of that LOCAL driver unless it is an atomic clock. No reason to panic and shoot that server, the score will drop below the +5 line in a day or so. regards, Jan _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
