Once upon a time, Gary Buhrmaster <gary.buhrmaster@xxxxxxxxx> said: > Personally, I have been using systemd-timesyncd for > quite some time on the vast majority of my systems > and am quite satisfied with it, but I believe that > changing from chrony to systemd-timesyncd was > considered too big of a last minute change since > we are in the final blocker stage of a release. Certainly - I was just looking for a more general solution to non-RTC systems going forward. Ideally, there could be something triggered by a lack of an RTC, but it looks like systemd path units cannot work based on a path (e.g. /dev/rtc) _not_ existing. That's unfortunate, that would make it easy. -- Chris Adams <linux@xxxxxxxxxxx> _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
