NTPSTAT(1)

πŸ“¦
version 0.6 Β· 2 versions
, in centos-stream 10, centos-stream 9, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable

πŸ’– NTPSTAT β€” bestie edition πŸ’–

okay so this is ntpstat(1), a little section 1 manual page, and honestly? it's giving "tiny script, huge main character energy." she prints NTP synchronisation status. that's it. that's the whole job. and she ATE. ✨


✨ NAME ✨

ntpstat β€” Print NTP synchronisation status πŸ•πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

ntpstat [-m MAXERROR]

like… one optional flag. we love a low-maintenance queen. πŸ‘‘


🌸 DESCRIPTION 🌸

so ntpstat is a script, and what she does is print a lil brief summary of your system clock's synchronisation status β€” but ONLY when the ntpd or chronyd daemon is actually running, bestie. no daemon, no tea. πŸ™ˆ

when she does run, she spills all of this:

  • the time source (an NTP server or a reference clock) that your system clock is currently synchronised to
  • its stratum
  • how often the server gets polled
  • the maximum estimated error of the clock

and the way she gets all that info is by calling up her besties ntpq or chronyc and asking the daemon directly. queen never guesses, she ASKS. 🫢

okay now the important lore. following the NTPv4 specification (RFC 5905): if your time source becomes unreachable and there are no other sources that could be selected, the status of the clock will still be "synchronised" β€” but the maximum error will be slowly increasing. so like… technically fine? technically?? it's giving "smiling through the pain" 😭 the error is literally creeping up on you and the status is out here saying everything's chill.

exit statuses β€” memorize these, they're the whole vibe check:

  • 0 β€” the clock is synchronised βœ… slay
  • 1 β€” the clock is not synchronised πŸ’€
  • 2 β€” the status could not be determined, e.g. when the daemon is not running 🀷
  • 3 β€” an invalid command-line option was specified πŸ™ƒ

πŸ’… OPTIONS πŸ’…

  • -m MAXERROR β€” specify a maximum acceptable error of the clock, in milliseconds. so if the clock IS synchronised, but its maximum estimated error is larger than MAXERROR, or is unknown, then ntpstat will exit with a status of 1. yes bestie, she WILL call it out. that's boundaries. πŸ’–
  • -h β€” print a help message and exit. the classic. the icon. the escape hatch. 🌈

⭐ SEE ALSO ⭐

ntpd(8), ntpq(8), chronyd(8), chronyc(1)

the whole friend group, fr fr πŸ¦‹


and that's the page!! this was ntpstat, from the NTPSTAT(1) manual (section 1, general commands manual, the classic). go check your sync status bestie, and remember: "synchronised" with a slowly growing error is still technically synchronised. iykyk. πŸ’œπŸŽ€

πŸ“¦ where this page comes from