Comment 1 for bug 1849156

Revision history for this message
Paul Buonopane (zenexer) wrote :

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.