Discussion:
[chrony-users] Chrony 3.1 on aarmv7
Robert Moskowitz
2017-08-22 13:22:59 UTC
Permalink
I an setting up a Fedora 26 image on a Cubieboard, not battery RTC.

F26 has v 3.1:

chrony-3.1-4.fc26.armv7hl.rpm

On my Centos7 systems with Chrony 2.1.1, I have had to:

cat <<EOF>/etc/sysconfig/chronyd || exit 1
OPTIONS=" -s"
EOF

and

cat <<EOF>>/etc/chrony.conf || exit 1
rtcdevice /dev/doesnotexist
EOF

I remember that more recent versions of Chrony better ways of handling
no battery, but I can't find that old message. So can I please have a
reminder of how to config 3.1 for no battery.

Thanks
--
To unsubscribe email chrony-users-***@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-***@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email ***@chrony.tuxfamily.org.
Miroslav Lichvar
2017-08-22 17:35:22 UTC
Permalink
Post by Robert Moskowitz
cat <<EOF>>/etc/chrony.conf || exit 1
rtcdevice /dev/doesnotexist
EOF
I remember that more recent versions of Chrony better ways of handling no
battery, but I can't find that old message. So can I please have a reminder
of how to config 3.1 for no battery.
The only difference is that with 3.1 it's no longer necessary to set
rtcdevice to a non-existent device. Even if it exists and it's a
working RTC, chronyd -s will not set the system clock to the RTC if
its time is before the last modification time of the drift file.
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-***@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-***@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email ***@chrony.tuxfamily.org.
Loading...