Marek Marczykowski-Górecki ee3950a3aa pm-utils: use qvm-sync-clock --force instead of manual qvm-run ... After suspend VMs clocks are desynchronized in most cases (because VMs were paused). Since directly after suspent there may be no network access, normal `qvm-sync-clock` call isn't good (it aborts if NTP call fails). But with new `qvm-sync-clock --force` switch, it sync VMs even if NTP is unreachable. QubesOS/qubes-issues#1728		2016-02-22 22:24:04 +01:00
..
01qubes-sync-vms-clock	pm-utils: use qvm-sync-clock --force instead of manual qvm-run	2016-02-22 22:24:04 +01:00
51qubes-suspend-netvm	pm-utils: do not load PM_FUNCTIONS - not used in our scripts	2013-11-06 15:42:59 +01:00
52qubes-pause-vms	pm-utils: try to suspend the VMs instead of just pause	2013-10-23 21:59:29 +02:00
qubes-suspend.service	pm-utils: add missing qubes-sync-vms-clock script to systemd service	2013-12-10 14:27:48 +01:00