On Fri, 21 Apr 2017, Robert Moskowitz wrote:



On 04/21/2017 08:35 AM, Miroslav Lichvar wrote:
On Fri, Apr 21, 2017 at 08:26:31AM -0400, Robert Moskowitz wrote:
On 04/21/2017 06:21 AM, Miroslav Lichvar wrote:
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 should be in chrony.conf. It specifies the path to the RTC device,
which is /dev/rtc by default.

OK. I went to https://chrony.tuxfamily.org/doc/devel/chrony.conf.html to read up a bit on chronyd.conf

And I am assuming that I am pointing to the default /dev/rtc and just add the file.

If you have
rtcdevice /dev/existingfile
(where "exxistingfile" means a file already in /dev, usually /dev/rtc or
/dev/rtc0) then chrony will try to read at boot the rtc. If that file does not
exist then it uses the date from the drift file


Got it.

thanks



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

OPTIONS= -s

Actually, that could go into the chrony systemd file
/usr/lib/systemd/system/chronyd.service
instead. Not all linux systems have /etc/sysconfig/chronyd files


Yes. If there are multiple options, I think they need to be in double
quotes, e.g. OPTIONS="-s -4".



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


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