| Re: [chrony-users] Chrony 3.1 on aarmv7 |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Chrony 3.1 on aarmv7
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 22 Aug 2017 19:35:22 +0200
- Authentication-results: ext-mx01.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx01.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 74EAF81E17
On Tue, Aug 22, 2017 at 09:22:59AM -0400, Robert Moskowitz wrote:
> 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-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.