Re: [chrony-users] Chrony setup using RTC as fallback

[Miroslav Lichvar <mlichvar@xxxxxxxxxx>]

On Wed, Nov 18, 2015 at 01:39:40PM +0100, Mauro Condarelli wrote:
> >>4) wait for network to go up
> >>5) sync time THEN
> >>5.1) IF net time > sysclock THEN sysclock = net time
> >>5.2) IF net time < sysclock THEN slow sysclock TILL sysclock == net time
> >chronyd has only one step threshold for both directions, so you would
> >probably need to remove the makestep directive from the config and do
> >that step manually in the "up" script instead. E.g.
> I assume You mean to add it to dhcpcd "BOUND" signal, right?

I'm not very familiar with the dhcpcd configuration. The commands
should be executed when the network is working, not sooner otherwise
the measurements would fail.

> >chronyc online
> >chronyc burst 4/4
> >sleep 10
> >chronyc tracking | grep -q 'System time.*slow' && chronyc makestep
> Added, even if it's unclear to me what this burst command really does (I read the Manual!).

It tells chronyd to make four measurements with only 2 second interval
between them, so the clock is updated in few seconds instead of 3
minutes it would need with normal polling.

-- 
Miroslav Lichvar

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