> Le 9 janv. 2019 à 22:52, chorowit...@scarsdaleschools.org a écrit : > > On Wednesday, March 3, 2004 at 11:38:29 PM UTC-5, Yoshinobu Onozuka wrote: >> Hello, >> >> >> >> I was using NTPD referring to two timeservers like the following setting. >> >> The contents of ntp.conf >> >> Server 172.16.0.1 minpoll 4 maxpoll 4 >> >> Server 172.16.125.92 minpoll 4 maxpoll 4 >> >> >> (minpoll , maxpoll=4 for test) >> >>
Have you never heard of the ancient truth that « A man with two clocks cannot know what the time is » . So NTP can not decide which server is good , so they both get flagged. You need to add some more servers. Have at least 5. >> >> NTPD version 4.1.x was used so far and it was working normally but >> >> when NTPD was updated to version 4.2.0, two timeservers became >> >> judged to be falsetickers. >> >> >> >> The output of ntpq - p >> >> remote refid st t when poll reach delay offset >> jitter >> >> ============================================================================ >> == >> >> x172.16.0.1 .TJJY. 1 u 12 16 377 0.470 0.082 >> 0.069 >> >> x172.16.125.92 .TJJY. 1 u 15 16 377 0.488 7.433 >> 0.226 >> >> >> >> The timeservers correct their time from the telephone JJY service(JST) via >> the telephone line. >> >> The time correction precision of the timeserver is 20 ms of +- / a day. >> >> Generally, once a day, they call at a different timing and they correct. >> >> >> >> Doesn't NTPD4.2.0 permit a time error among these two timeservers? >> >> I hope that the option which can set the latitude of the falseticker >> judgment is >> >> implemented to NTPD. >> >> >> >> Thank you. > > _______________________________________________ > questions mailing list > questions@lists.ntp.org > http://lists.ntp.org/listinfo/questions I am not a a vegetarian because I love animals. I’m a vegetarian because I hate plants. _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
