<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ntp on toorun.dev</title><link>https://toorun.dev/tags/ntp/</link><description>Recent content in ntp on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 24 Jul 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/ntp/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux NTP: Practical Settings and Usage</title><link>https://toorun.dev/posts/linux-ntp-time-sync-settings-chrony-timesyncd-ntpd/</link><pubDate>Fri, 24 Jul 2026 10:00:00 +0000</pubDate><guid>https://toorun.dev/posts/linux-ntp-time-sync-settings-chrony-timesyncd-ntpd/</guid><description>Linux NTP (Short Practical Guide) Accurate time is required for TLS, logs, monitoring, cron jobs, and distributed systems. In Linux, use one time-sync service only.
1) Check current time sync status timedatectl status Look for:
System clock synchronized: yes NTP service: active 2) Recommended choice: chrony chrony is usually the best default for servers and unstable networks.
Install and enable:
# Debian/Ubuntu sudo apt update &amp;amp;&amp;amp; sudo apt install -y chrony sudo systemctl enable --now chrony # RHEL/CentOS/Fedora sudo dnf install -y chrony sudo systemctl enable --now chronyd Basic config file:</description></item></channel></rss>