> The recommended way to use NTP is to run a daemon which will continue to run in the background ensuring your clock is accurate You'd might not want to have a

> The recommended way to use NTP is to run a daemon which will continue to run in the background ensuring your clock is accurate You'd might not want to have a daemon running in the background or install extra software in certain circumstances. If you're using a lightweight solution such as systemd-timesyncd or ntpdate+cron it will only query one server, and you end up with the wrong time for ~30 minutes, which can cause major downtime or data corruption in certain circumstances. Even if you're able to use a better client like chrony, it still doesn't solve the issues with leap seconds without extra configuration, which can cause the time to jump or move backwards, which can cause major downtime, e.g. https://blog.cloudflare.com/how-and-why-the-leap-second-affected-cloudflare-dns/ https://blog.cloudflare.com/how-and-why-the-leap-second-affe... https://www.techspot.com/news/49229-leap-second-bug-amazon-ec2-outage-brought-down-major-websites.html https://www.techspot.com/news/49229-leap-second-bug-amazon-e...