[ntp:questions] Re: NMEA driver clk_fault - OK. Thanks

David L. Mills mills at udel.edu
Thu Sep 18 02:30:22 UTC 2003


It is the convention in many drivers to clockstats the timecode message
at intervals not less than the poll interval. If you don't want to see
these messages, don't enable clockstats. Then, for additional detail,
most drivers observe the convention that fudge flag4 produces more
detail in special cases. All this assumes the driver code is operating
correctly and what you want to see is the clock antics in detail.
Finally, if you don't trust the code, then turn on the debug flag and
produce detail for trace.

Good philosophy in these things is to avoid being too cute. The fact a
message is picked up somewhat later by poll than actually produced is
not a problem, as long as the timestamp upon arrival is struck and the
difference computed later. For my several drivers the goal is simplicity
in function and implementation without compromising accuracy. Not all
the drivers salute this mantra.

Just convention, not law.


More information about the questions mailing list