core-agent-linux/vm-systemd/qubes-sync-time.service

[Unit]
Description=Update time from ClockVM
After=qubes-qrexec-agent.service
ConditionPathExists=!/var/run/qubes-service/clocksync

[Service]
ExecStart=/usr/bin/qvm-sync-clock
User=root
clock synchronization rewrite clock synchronization mechanism rewritten to use systemd-timesync instead of NtpDate; at the moment, requires: - modifying /etc/qubes-rpc/policy/qubes.GetDate to redirect GetDate to designated clockvm - enabling clocksync service in clockvm ( qvm-features clockvm-name service/clocksync true ) Works as specified in issue listed below, except for: - each VM synces with clockvm after boot and every 6h - clockvm synces time with the Internet using systemd-timesync - dom0 synces itself with clockvm every 1h (using cron) fixes QubesOS/qubes-issues#1230 2017-07-06 23:37:26 +02:00			`[Unit]`
			`Description=Update time from ClockVM`
Delay qubes-sync-time service after qrexec is started The qubes-sync-time needs qrexec running to work, so set start order appropriately. 2019-06-25 04:19:56 +02:00			`After=qubes-qrexec-agent.service`
clock synchronization rewrite clock synchronization mechanism rewritten to use systemd-timesync instead of NtpDate; at the moment, requires: - modifying /etc/qubes-rpc/policy/qubes.GetDate to redirect GetDate to designated clockvm - enabling clocksync service in clockvm ( qvm-features clockvm-name service/clocksync true ) Works as specified in issue listed below, except for: - each VM synces with clockvm after boot and every 6h - clockvm synces time with the Internet using systemd-timesync - dom0 synces itself with clockvm every 1h (using cron) fixes QubesOS/qubes-issues#1230 2017-07-06 23:37:26 +02:00			`ConditionPathExists=!/var/run/qubes-service/clocksync`

			`[Service]`
			`ExecStart=/usr/bin/qvm-sync-clock`
Delay qubes-sync-time service after qrexec is started The qubes-sync-time needs qrexec running to work, so set start order appropriately. 2019-06-25 04:19:56 +02:00			`User=root`