core-agent-linux/vm-systemd/chronyd.service.d/30_qubes.conf

[Unit]
ConditionPathExists=|/var/run/qubes-service/clocksync
ConditionPathExists=|/var/run/qubes-service/ntpd
After=qubes-sysinit.service
vm/init: introduce SystemD startup scripts 2012-01-10 12:10:16 +01:00			`[Unit]`
Fix starting time synchronization service systemd-timesyncd.service isn't enough, for various reasons: - it is started too early in the boot process - files in /var/run/qubes-services are not yet there - by default it does only one shot synchronization, and there is no network at that early boot time yet - by default use-ntp is set to "no" So, in addition, enable actual ntp client. Fixes QubesOS/qubes-issues#3210 2017-11-03 03:12:55 +01:00			`ConditionPathExists=\|/var/run/qubes-service/clocksync`
			`ConditionPathExists=\|/var/run/qubes-service/ntpd`
systemd: order units checking for qubes-service after qubes-sysinit Files in /var/run/qubes-service are created by qubes-sysinit.service. So defer that condition check after that service start. Thanks @adrelanos for the report. Fixes QubesOS/qubes-issues#1985 2016-05-12 00:15:14 +02:00			`After=qubes-sysinit.service`