On Fri, 21 Apr 2017, Robert Moskowitz wrote:

Gaining understanding...

On 04/21/2017 06:21 AM, Miroslav Lichvar wrote:
On Fri, Apr 21, 2017 at 05:59:12AM -0400, Robert Moskowitz wrote:
I was looking at the man for chronyd, and saw that the man for 2.1.1 says it
uses the drift file:

If chronyd doesn't support the RTC on your computer or there
is
               no RTC installed, the system clock will be set with this
option
               forward  to  the time of the last modification of the drift
file
               (specified by the driftfile directive)  to  restore the
system
               time at which chronyd was previously stopped.
You are right. The difference between 2.1.1 and 2.2 actually is that
2.1.1 uses the driftfile only when the RTC is missing. If there is an
RTC, but it is in the past (e.g. it has no battery to keep the time
when the system was powered off), the driftfile will not be used to
restore the system time.

However, you could force chronyd to ignore the RTC by setting
rtcdevice to a nonexistent device and always use the driftfile, e.g.

rtcdevice /dev/doesnotexist

Where do I get the command, rtcdevice? It is not on my system. Then how do I run it? Do I add an ExecStartPre= to the chronyd.service file?

It is a line in chrony.conf. It is not a separate command.


And do I create a /etc/sysconfig/chronyd with the single line:

OPTIONS= -s

?



What does the rtcsync in chronyd.conf do?
It tells the kernel to periodically set the RTC to the system time.
With no battery, that would probably be useful only for reboots.

Got it.


--
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.

Reply via email to