[ntp:questions] Re: Clock type 30 invalid?

Paul Croome Paul.Croome at softwareag.com
Tue Jan 20 11:05:10 UTC 2004

"Richard B. Gilbert" <rgilbert88 at comcast.net> wrote in message news:<Af2dnYwgPd26DpHdRVn-vA at comcast.com>...
> I used the default build procedures.  ./configure, make, etc.   


To include support for the Motorola M12:

   ./configure --enable-ONCORE

If the M12 is the only reference clock in your system,
you can generate a smaller object file with:

   ./configure --disable-all-clocks --enable-ONCORE

For more information:
   ./configure --help
and see also html/config.html.
Caveat: There are two distinct configuration phases for NTP:
compile-time (see above) and run-time (controlled by /etc/ntp.conf).
The NTP doc doesn't always distinguish clearly what's which.

BTW: You shouldn't fudge the GPS timeserver to stratum=0.
Stratum 0 is notionally assigned to the Motorola hardware,
in your case, and to reference clocks in general;
strata 1 thru 15 are assigned to the NTP timeservers;
stratum 16 usually means 'out of order'.
Usually it's OK to let NTP figure out the stratum, i.e.
just take the default.


More information about the questions mailing list