Qubes/core-agent-linux
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
4f55a3b085
core-agent-linux/vm-systemd/systemd-timesyncd.service.d/30_qubes.conf

4 lines
88 B
Plaintext
Raw Normal View History

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]
Fix systemd-timesyncd.service startup Add After=qubes-sysinit.service to avoid startup condition being evaluated before initializing qubes-service directory. Fixes QubesOS/qubes-issues#3333
2018-02-13 02:14:08 +01:00
ConditionPathExists=/var/run/qubes-service/clocksync
After=qubes-sysinit.service
Reference in New Issue Copy Permalink