Re: [chrony-dev] Bug -- interaction between ntpdate and chronyd at bootup -- will never sync up

[Ed W <lists@xxxxxxxxxxxxxx>]

Hi

> Since the clock starts out at Dec 31 1969 18:00:00 CST, it is
> important to set the date/time to approximately the actual date/time
> as soon as possible in the bootup sequence.

Not disagreeing, but could you define *why* and then someone might give 
you some ideas on fixing that, as much as getting chrony going?

If your goal is simply a monotic clock, then you could use the swclock 
idea from gentoo's openrc. It basically relies on there being some file 
with a recent timestamp on it (set it at shutdown, using cron, etc), 
then when you boot you simply read the file timestamp and go with that 
as a clock estimate.

Clearly the clock will be an unknown amount wrong, but for some purposes 
(eg monotonically increasing clock) it may be sufficient for your 
requirements?


I use something similar, get a rough time initially, either from RTC or 
using swclock, then invest additional time getting a much closer 
timestamp from chrony and eventually gpsd.

Good luck

Ed W

--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.