Hal Murray wrote:
[email protected] said:
Only issue for 8.0 was to ensure the real time clock driver was
enabled or the initial time error would often be too large.
There is a command line switch that allows ntpd to start on systems that have
a bogus initial date/time.
> From the man page:
-g, --panicgate
Allow the first adjustment to be Big. This option may
appear an unlimited number of times.
Normally, ntpd exits with a message to the system log if
the offset exceeds the panic threshold, which is 1000 s
by default. This option allows the time to be set to any
value without restriction; however, this can happen only
once. If the threshold is exceeded after that, ntpd will
exit with a message to the system log. This option can be
used with the -q and -x options. See the tinker configu-
ration file directive for other options.
I was aware of that, but using the real time clock seems to work better
for subsequent power on, once the real time clock is set correctly.
However with 8.0 the real time clock driver had to be specifically
included in the kernel config file whereas in 7.2 it was automatically
included.
Bruce
_______________________________________________
time-nuts mailing list -- [email protected]
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
