From 421c170933a5efc650b1666bf6c9a8bf541370af Mon Sep 17 00:00:00 2001 From: Thomas Lamprecht Date: Mon, 25 Apr 2022 17:49:33 +0200 Subject: [PATCH] drop enabling timesyncd, wrong since chrony switch & unnecessary anyway It should actually fail since the switch to chrony, but syscmd only returns the exit code and we did not check it. Shortly thought about checking for the existence of "$targetdir/lib/systemd/system/chrony.service" and enable chrony.service in that case, but that is unnecessary too, as we know due to this bogus enable timesyncd which never stopped chrony to run happily enabled after installation anyway. Signed-off-by: Thomas Lamprecht --- proxinstall | 3 --- 1 file changed, 3 deletions(-) diff --git a/proxinstall b/proxinstall index d84b3c6..04298e2 100755 --- a/proxinstall +++ b/proxinstall @@ -1740,9 +1740,6 @@ _EOD # create /etc/aliases.db (/etc/aliases is shipped in the base squashfs) syscmd("chroot $targetdir /usr/bin/newaliases"); - # enable NTP (timedatectl set-ntp true does not work without DBUS) - syscmd("chroot $targetdir /bin/systemctl enable systemd-timesyncd.service"); - unlink "$targetdir/proxmox_install_mode"; # set timezone -- 2.39.2