After a quick check it looks like this service is still in inactive (dead) state even after a reboot.
ubuntu@kernel04:/lib/systemd$ sudo systemctl status systemd-timesyncd
● systemd-timesyncd.service
Loaded: masked (Reason: Unit systemd-timesyncd.service is masked.)
Active: inactive (dead)
ubuntu@kernel04:/lib/systemd$ file /lib/systemd/system/systemd-timesyncd.service
/lib/systemd/system/systemd-timesyncd.service: cannot open `/lib/systemd/system/systemd-timesyncd.service' (No such file or directory)
And there is no "systemd-timesyncd.service" file at where is should be.
So yeah it's not running, our testing tool did not check the state first before trying to stop / start it.
$ sudo systemctl edit systemd-timesyncd
Cannot edit systemd-timesyncd.service: unit is masked.
Hello Dimitri,
After a quick check it looks like this service is still in inactive (dead) state even after a reboot.
ubuntu@ kernel04: /lib/systemd$ sudo systemctl status systemd-timesyncd timesyncd. service timesyncd. service is masked.) kernel04: /lib/systemd$ file /lib/systemd/ system/ systemd- timesyncd. service system/ systemd- timesyncd. service: cannot open `/lib/systemd/ system/ systemd- timesyncd. service' (No such file or directory)
● systemd-
Loaded: masked (Reason: Unit systemd-
Active: inactive (dead)
ubuntu@
/lib/systemd/
And there is no "systemd- timesyncd. service" file at where is should be.
So yeah it's not running, our testing tool did not check the state first before trying to stop / start it.
$ sudo systemctl edit systemd-timesyncd timesyncd. service: unit is masked.
Cannot edit systemd-
Let me see if I can un-mask it.