[ntp:questions] 4.2.0 ntptrace problem when sync'ed to local closk

Jan Ceuleers janspam.ceuleers at computer.org
Wed Oct 15 18:07:50 UTC 2003


I have just built and installed 4.2.0 on my Red Hat Linux 7.2 system and
a couple of minutes after starting the daemon I had the following
transient problem with ntptrace:

penta: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: stratum 11, offset 0.000000, root distance 0.000000
(ad infinitum)

Before the above happened ntptrace had worked correctly (that is: just
after starting ntpd and the system had not yet achieved
synchronisation).

Once synchronisation has been achieved ntptrace also starting working
OK:

penta: stratum 1, offset 0.000359, root distance 0.000000, refid 'DCFa'

It therefore looks to me like the problem is that ntptrace does not
recognise that 127.127.1.0 is the local clock and that it should stop
tracing when this address is encountered.

Cheers, Jan



More information about the questions mailing list