This is an automated email from git. It was enerated because a ref
change was pushed to the repository "chrony/chrony.git".
The branch, master has been updated
via a080d00352cb5296239f25d87275035c2fac325e (commit)
via 5fb0a9d53b371f6d419fcbeb83251421cb3a42e5 (commit)
via
> 3. In an extreme case, the only permanent storage, with r/w access,
> is a small
> NVRAM in RTC. The estimated system clock error/drift ca be stored
> there.
No, there is no linux way of putting the drift rate into the rtc that I
know
of.
I read it from NVRAM and create a drift file
2. The kernel writes to RTC at a 0.5 second mark so the error can be
minimize in case of
power outage and no access to NTP servers.
No idea what you mean here. Yes, in order to write to the rtc, you have to
stagger the write because the rtc is weird. But what has this to do with
your
desire
On Fri, 14 May 2010, Piotr Grudzinski wrote:
> 2. The kernel writes to RTC at a 0.5 second mark so the error can be
> minimize in case of
> power outage and no access to NTP servers.
No idea what you mean here. Yes, in order to write to the rtc, you have to
stagger the write because the
