[ntp:questions] Re: Correcting my time servers clock drift on Alpha ES40s / Tru64

Tom Smith smith at cag.zko.hp.com
Sun Oct 23 18:28:45 UTC 2005

Here are the messages that seemed mysterious in the original post:

20 Jul 17:40:44 xntpd[764]: logging to file /var/adm/ntpd.log
20 Jul 17:40:44 xntpd[764]: ntpd 4.0.98a Wed Oct 16 17:36:24 EDT 2002
20 Jul 17:40:44 xntpd[764]: precision = 976 usec
20 Jul 17:40:44 xntpd[764]: kern_enable is 1
20 Jul 17:40:44 xntpd[764]: using kernel phase-lock loop 0040
20 Jul 17:40:44 xntpd[764]: frequency initialized -5.490 from
20 Jul 17:40:44 xntpd[764]: using kernel phase-lock loop 0041

I suggested that these were probably messages that had changed between
4.0.98a and the current development versions.

Here's what I find in the project's 4.0.99 distribution (other than the
version message). 4.0.98a is likely the same, but if anybody still has a copy
around 9and cares), they can check.

In ntp_config.c:

                                            msyslog(LOG_NOTICE, "logging to file %s", ntp_optarg);
                                        msyslog(LOG_NOTICE, "logging to file %s", tokens[1]);

In ntp_proto.c:

             msyslog(LOG_INFO, "precision = %ld usec", val);

         msyslog(LOG_DEBUG, "kern_enable is %d", kern_enable);

In ntp_loopfilter.c:

                             "using kernel phase-lock loop %04x",

In ntp_util.c

                msyslog(LOG_INFO, "frequency initialized %.3f from %s",
                     old_drift, stats_drift_file);

Hopefully, we can leave this topic now, since it has no relevance to the
original poster's question.


More information about the questions mailing list