| Re: [chrony-dev] Let the kernel write the sys clock to RTC |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
On Thu, 13 May 2010, Piotr Grudzinski wrote:
From: "Bill Unruh" <unruh@xxxxxxxxxxxxxx>
Curnow purposely disabled the 11 min mode for all the above reasons. Why
would
you want to have it?
1. I pretty much agree with the following:
http://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-dev/2010/04/msg00034.html
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 that the kernel write to it every 11 min. chrony handles the rtc
properly
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.
And systems with flash based file systems have limited number of write cycles
so
frequent logging is not recommended.
Fine. But it does not do frequenct logging for the rtc drift file.
Regards,
Piotr
---
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.
--
William G. Unruh | Canadian Institute for| Tel: +1(604)822-3273
Physics&Astronomy | Advanced Research | Fax: +1(604)822-5324
UBC, Vancouver,BC | Program in Cosmology | unruh@xxxxxxxxxxxxxx
Canada V6T 1Z1 | and Gravity | www.theory.physics.ubc.ca/
---
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.