[ntp:questions] Re: Correcting my time servers clock drift on Alpha ES40s / Tru64
David L. Mills
mills at udel.edu
Mon Oct 24 04:44:37 UTC 2005
It matters not what the prefix says xntpd (NTPv3), but the version
claimed in the banner is ntpd (NTPv4). The last time my paws fondled
xntpd was seven years ago and that was version 3.5. Whether somebody
updated to NTPv4 and changed the name of the program to xntpd is very
retro, bot possible, and in that case claiming a recent NTPv4 version
suggests cyberterrorist. In any case, the comment you cite in
ntp_loopfilter.c is simply not there. Maybe it should be.
Over the years there have been many occasions when folks have added
commentary to the distribution to "fix" or "explain" something. Makes me
nervous, but I don't take those comments out.
Tom Smith wrote:
> David L. Mills wrote:
>> Note the prefix of your log messages. It is not possible for the
>> kernel to simulate that. I conclude the source has been changed. I
>> have no problem at all with that, but the only way I can be completely
>> confident with help is with the unabridged version that leaves here.
> The prefix on log messages comes strictly from the name of the executable
> (and its PID), not from the bits within it. It is used to show the source
> of the message. The version is shown in the log at the time (x)ntpd starts:
> 20 Jul 17:40:44 xntpd: ntpd 4.0.98a Wed Oct 16 17:36:24 EDT 2002
> To the best of my knowledge, all versions of (x)ntpd announce their actual
> versions in this way.
> None of this has anything to do with the original question, of course,
> which was, essentially, "Why do my clocks that have no fixed reference
> not keep accurate time?".
More information about the questions