From 8c0643092b919fe9e08baf34527e7cb48550fefb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Marek=20Marczykowski-G=C3=B3recki?=
 <marmarek@invisiblethingslab.com>
Date: Mon, 8 Feb 2016 04:49:14 +0100
Subject: [PATCH] Use qubes.SetDateTime instead of direct call in post-suspend
 time sync

Fixes QubesOS/qubes-issues#1728
---
 pm-utils/01qubes-sync-vms-clock | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pm-utils/01qubes-sync-vms-clock b/pm-utils/01qubes-sync-vms-clock
index 7b4a395..5bb8516 100755
--- a/pm-utils/01qubes-sync-vms-clock
+++ b/pm-utils/01qubes-sync-vms-clock
@@ -6,7 +6,7 @@ sync_qubes_vms_wallclock()
     DATE=$(date)
     echo
     echo "Syncing VMs clock to: $DATE"
-    qvm-run --all -u root "date -s \"$DATE\""
+    qvm-run --all -u root --localcmd="date -u -Iseconds" "qubes.SetDateTime dom0"
     # Then try to sync from the network
     /usr/bin/qvm-sync-clock &
 }