Ntpq: Difference between revisions
Jump to navigation
Jump to search
(Created page with "== ntpq -p == === Active Sync Time Source === # Look for the asterisk * in the first column, which identifies your currently selected active time source. # The reach column should ideally be 377 (octal), confirming the server has been successfully contacted over the last 8 polls. # The offset should be a very low number (typically under 100 milliseconds), showing how far off your clock is from the server. <pre> # ntpq -p remote r...") |
No edit summary |
||
| Line 28: | Line 28: | ||
3 17769 b414 yes yes none candidate reachable 1 | 3 17769 b414 yes yes none candidate reachable 1 | ||
</pre> | </pre> | ||
== keywords == | |||
Latest revision as of 07:00, 7 July 2026
ntpq -p
Active Sync Time Source
- Look for the asterisk * in the first column, which identifies your currently selected active time source.
- The reach column should ideally be 377 (octal), confirming the server has been successfully contacted over the last 8 polls.
- The offset should be a very low number (typically under 100 milliseconds), showing how far off your clock is from the server.
# ntpq -p
remote refid st t when poll reach delay offset jitter
=======================================================================================================
*10.1.1.1 169.254.0.1 3 u 1 64 377 31.7132 -2.6834 1.7580
+10.1.2.1 169.254.0.1 3 u 62 64 377 31.7588 -2.6430 1.7581
+10.1.3.1 169.254.0.1 3 u 62 64 377 31.7444 -2.6400 1.7500
List associations
ntpq -c associations
Sample:
ind assid status conf reach auth condition last_event cnt =========================================================== 1 17767 b61a yes yes none sys.peer sys_peer 1 2 17768 b414 yes yes none candidate reachable 1 3 17769 b414 yes yes none candidate reachable 1