Bug #12818
open
ntpq(1m) -w flag undocumented
0%
Description
The ntpq manpage doesn’t mention the -w flag (it does work though, check the output of ntpq -p vs ntpq -pw).
FreeBSD has it: https://www.freebsd.org/cgi/man.cgi?query=ntpq
Updated by John Gardner over 3 years ago
ntpq -pw certainly works
bash-5.0$ ntpq -p server.lan
remote refid st t when poll reach delay offset jitter
==============================================================================
*bitburger.simon .GPS. 1 u 685 1024 377 18.990 0.784 1.754
-any.time.nl 126.11.196.147 2 u 989 1024 377 10.885 3.074 0.748
-time.cloudflare 10.26.8.188 3 u 287 1024 377 10.225 1.697 0.655
#ntp3.ds.network 162.159.200.123 4 u 492 1024 377 60.297 1.743 1.282
+pauseq4vntp1.da 203.35.83.242 2 u 828 1024 377 11.161 1.984 1.135
-ec2-13-55-50-68 203.206.205.83 3 u 877 1024 377 12.951 -1.173 0.755
#ntp02.lagoon.nc 8.145.32.135 2 u 286 1024 377 35.405 -16.574 1.376
-time.cloudflare 10.26.8.188 3 u 1007 1024 377 10.317 1.788 0.586
-cosima.470n.act 202.6.131.118 2 u 267 1024 377 14.489 -2.628 4.350
-speedtest.cribb 162.159.200.123 4 u 610 1024 377 11.878 0.302 0.600
any.time.nl .INIT. 16 u - 1024 0 0.000 0.000 0.000
2001:19f0:5801: .INIT. 16 u - 1024 0 0.000 0.000 0.000
time.cloudflare .INIT. 16 u - 1024 0 0.000 0.000 0.000
time.cloudflare .INIT. 16 u - 1024 0 0.000 0.000 0.000
#220-158-215-20. 202.46.178.18 2 u 582 1024 377 34.412 -8.345 0.747
122.252.188.99 202.46.178.18 2 u 57h 1024 0 35.965 2.577 0.000
-mika.470n.act.t 130.95.179.80 2 u 177 1024 377 14.461 -2.352 3.932
+dns01.ntl02.pri 210.9.192.50 2 u 641 1024 377 16.386 1.488 0.496
172.16.16.255 .BCST. 16 B - 64 0 0.000 0.000 0.000
bash-5.0$ ntpq -pw server.lan
remote refid st t when poll reach delay offset jitter
==============================================================================
*bitburger.simonrumble.com
.GPS. 1 u 688 1024 377 18.990 0.784 1.754
-any.time.nl 126.11.196.147 2 u 992 1024 377 10.885 3.074 0.748
-time.cloudflare.com
10.26.8.188 3 u 290 1024 377 10.225 1.697 0.655
#ntp3.ds.network 162.159.200.123 4 u 495 1024 377 60.297 1.743 1.282
+pauseq4vntp1.datamossa.io
203.35.83.242 2 u 831 1024 377 11.161 1.984 1.135
-ec2-13-55-50-68.ap-southeast-2.compute.amazonaws.com
203.206.205.83 3 u 880 1024 377 12.951 -1.173 0.755
#ntp02.lagoon.nc 8.145.32.135 2 u 289 1024 377 35.405 -16.574 1.376
-time.cloudflare.com
10.26.8.188 3 u 1010 1024 377 10.317 1.788 0.586
-cosima.470n.act.tsgnl.co
202.6.131.118 2 u 270 1024 377 14.489 -2.628 4.350
-speedtest.cribbes.com
162.159.200.123 4 u 613 1024 377 11.878 0.302 0.600
any.time.nl .INIT. 16 u - 1024 0 0.000 0.000 0.000
2001:19f0:5801:1daa:5400:1ff:fe95:cf80 (dns.seby.io)
.INIT. 16 u - 1024 0 0.000 0.000 0.000
time.cloudflare.com
.INIT. 16 u - 1024 0 0.000 0.000 0.000
time.cloudflare.com
.INIT. 16 u - 1024 0 0.000 0.000 0.000
#220-158-215-20.broadband.telesmart.co.nz
202.46.178.18 2 u 585 1024 377 34.412 -8.345 0.747
122.252.188.99 202.46.178.18 2 u 57h 1024 0 35.965 2.577 0.000
-mika.470n.act.tsgnl.co
130.95.179.80 2 u 180 1024 377 14.461 -2.352 3.932
+dns01.ntl02.privatecloudco.com
210.9.192.50 2 u 644 1024 377 16.386 1.488 0.496
172.16.16.255 .BCST. 16 B - 64 0 0.000 0.000 0.000
bash-5.0$
Updated by Christoph Binner over 3 years ago
Yes, it works. It just isn’t documented in the man page.
Updated by Andy Fiddaman over 3 years ago
The ntp stuff comes from the distribution, not illumos-gate.
At least OmniOS has moved to ntpsec by default these days.
Updated by Christoph Binner about 3 years ago
This is solved for OmniOS with ntpsec in r151036, I suppose this ticket could be moved to the Openindiana tracker.