I realize that the title makes it sound as though this is intended behavior. To be clear, in this scenario, neither systemd-timesyncd.service nor ntp.service start. It's not just systemd-timesyncd.service that doesn't start, as that would be intended behavior.
I realize that the title makes it sound as though this is intended behavior. To be clear, in this scenario, neither systemd- timesyncd. service nor ntp.service start. It's not just systemd- timesyncd. service that doesn't start, as that would be intended behavior.