By default, *dhcpcd* generates a "complete" `chrony.conf` file using the NTP servers specified in the DHCP lease, and then restarts the Chrony daemon. This is unnecessary, as *chrony* can reload its list of sources without restarting, and also problematic in our case. For one thing, *dhcpcd* tries to write to `/etc/chrony.conf` directly, which is obviously impossible when the root filesystem is immutable. Fortunately, it is flexible enough to be configured to leave `/etc/chrony.conf` alone and generate a different file and then tell *chrony* to reread it. The *chrony-wait.service* unit introduces a delay into the system startup that allows follow-up units to wait until the system time is confirmed correct. The unit file itself was derived from the one included in the *chrony* package for Fedora. |
||
---|---|---|
.. | ||
dhcpcd.service.d | ||
local-fs.target.requires | ||
multi-user.target.wants | ||
rsyslog.service.wants | ||
chrony-wait.service | ||
copy-var.service | ||
fetch-sshkeys@.service | ||
gen-rsyslog-conf.service | ||
htop.service |