🚀 go-pugleaf

>>>>> On 6 Jun 91 18:25:23 GMT, ramus@WINDSAIL.NERSC.GOV (Joe Ramus) said:

[clockhopping (prevention of) patch removed]

Joe> How does one determine what version?
Joe> What is the version now available on louie.udel.edu ??

Joe> I wonder if the bug is fixed in the source on louie.udel.edu

The version on louie.udel.edu is still 1.3 (look in the version.c file
in the xntpd directory). Even if someone has forgotten to update the
version.c file, the bug is still present in that version!

This might also fix the problem experienced by 
net@opal.cs.tu-berlin.de (Oliver Laumann) in the Sun. I found this
problem when my network became rather delayed and unpredictable. This
caused xntp to keep chaning its mind about which clocks were 'good'.
Even though my system has a radio clock on it, it would still try and
switch to synching on a remote stratum-1. 

You can check to see if you have problems. If you use ntpq to
interrogate your server, then the symbols in column 1 (*.+) mean

*       The current clock source
+       A possible source. These should have low offsets and/or low dispersions
.       A candidate. These will be 'worse' than the '+' peers.

If these symbols 'look wrong' then you may suffer from clockhopping
and all the other bad things that flow from this.

Philip
--
Philip Gladstone         Dev Lab Europe, Data General, Cambridge, UK

    There did, however, remain the question of both the mysterious 60,000
    Altairian dollars paid yearly into his Brantisvogan bank account, and
    Zaphod Beeblebrox's highly profitable second-hand biro business.