Re: [chrony-users] Best way to force clock step at shutdown

[Miroslav Lichvar <mlichvar@xxxxxxxxxx>]

On Tue, Jan 12, 2016 at 07:05:51PM +0100, Hector Oron wrote:
> > Hm, with minpoll 8 (256 seconds) chronyd should have 3 samples per
> > source after about 9 minutes, so I'm not sure why 17 minutes is not
> > enough.
> 
> Probably I was too quick before, I have redone the test and it seems
> to work now.

Ok, great.

I just had an idea, if you only need to sync the RTC and not the
system clock, you could let chronyd do that continuously and not have
to do anything on shutdown. Disable the hwclock call (or whatever is
setting the RTC from the system clock on shutdown) and add the
rtcfile + rtcautotrim directives to chrony.conf. The RTC should be
kept close to the true time even if chronyd is slewing a large offset
in the system time. E.g.

rtcfile /var/lib/chrony/rtc
rtcautotrim 1

-- 
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.