Hello David, On Sunday, May 13, 2007 at 1:49:00 +0000, David L. Mills wrote:
> The current ntpd -gq code does not set the kernel frequency from the > frequency file, but it can be set using ntptime -f. It would be the right thing for ntpd -gq to set the frequency by itself. And of course it's well designed, so it does it. :-) | # ntptime -f 0 > /dev/null | # ntpd -gq | ntpd: time slew +0.047229s | # ntptime | grep ", frequency" | offset 0.000 us, frequency -2.218 ppm, interval 4 s, Corresponding syslog: | May 13 18:22:01 Ummon ntpd[126]: ntpd 4.2.5p20-o Mon Apr 2 17:32:22 UTC 2007 (3) | May 13 18:22:01 Ummon ntpd[126]: precision = 7.000 usec | May 13 18:22:01 Ummon ntpd[126]: ntp_io: estimated max descriptors: 256, initial socket boundary: 48 | May 13 18:22:01 Ummon ntpd[126]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled | May 13 18:22:01 Ummon ntpd[126]: Listening on interface #1 lo, 127.0.0.1#123 Enabled | May 13 18:22:01 Ummon ntpd[126]: Listening on interface #2 eth0, 192.168.7.7#123 Enabled | May 13 18:22:01 Ummon ntpd[126]: kernel time sync status 0040 | May 13 18:22:01 Ummon ntpd[126]: frequency initialized -2.218 PPM from /var/lib/ntp/ntp.drift | May 13 18:22:08 Ummon ntpd[126]: synchronized to 192.168.7.3, stratum 1 | May 13 18:22:08 Ummon ntpd[126]: time slew +0.047229 s Serge. -- Serge point Bets arobase laposte point net _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
