Kipton Moravec wrote:
> I have a local time server (Blue). When I execute ntptrace
>
> localhost: stratum 2, offset -0.008035, synch distance 0.104165
> clock3.redhat.com: stratum 1, offset 0.000001, synch distance 0.000325,
> refid 'CDMA'
>
> My workstation gets its time from Blue. When I execute ntptrace I get a
> request timed out.
>
> What do I have to do to make Blue respond to ntptrace?
>
> Kip
>
The short answer is to change Blue's restrict noquery in ntp.conf to
allow your workstation.
The long answer: I've been dabbling in Ruby to do some NTP analysis
stuff, and from the comments in my code:
## ntptrace in the NTP-4.x suite is a perl script that uses ntpq
# commands against successive hosts, thus it uses control messages,
# which are often filtered (by ntpd), but contain recorded offsets.
# Here we use the time messages, which usually are not filtered
# (would make NTP academic), but do not contain recorded offsets, so
# we have to work those out ourselves.
In practice, it's a different set of servers that work for my ntptrace
vs the NTP suite. The sets intersect somewhat.
--
Jeff Woolsey {woolsey,[EMAIL PROTECTED],[EMAIL PROTECTED]
Nature abhors a straight antenna, a clean lens, and unused storage capacity.
"Delete! Delete! OK!" -Dr. Bronner on disk space management
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
