ntpq: user variables, anybody use them?

[James Browning]

On Wed, Mar 10, 2021 at 2:16 PM Hal Murray <hmurray at megapathdsl.net> wrote:

>
> >> The server side of ntpq supports writing and reading things of the form
> >> "foo=bar". >
> >> I'm slightly surprised Eric hasn't riped that out by now. >
> >> Does anybody use it?  How/why?  ,,,
>
> > No, I don't. I had this foolish notion though (or it might've been
> Achim) not
> > long after (during?) the rainbow control debacle about prepending a
> modifier
> > character (say @ or such) to a variable which is a list of variables and
> it
> > would return all of the variables in that list.
>
> The current code has some slots marked DEF (default).   I think it is only
> used by ntpq sysinfo.  The implementation is "rv 0" or just "rv" with an
> empty
> list of names that it wants to retrieve.
>

 DEF is also implemented for 'cv #' and 'rv #', IIRC.


> My plan was to add more flags.  I'm happy with your @ suggestion.
>
> Please start collecting a list of things you would like to retrieve this
> way.
> The 2 that I use often are the NTS statistics and the MRU statistics:
> ntsinfo
> and monstats.
>

That does not seem to be how sysinfo works. There probably should
be a request for peoples' lists on the users, devel, and maybe
announce lists. The hopefully complete list (from ntpq) is as follows.

l_sysinfo="peeradr,peermode,leap,stratum,precision,rootdelay,rootdisp,rootdist,refid,reftime,sys_jitter,clk_jitter,clk_wander,authdelay"

l_kerninfo="koffset,kfreq,kmaxerr,kesterr,kstflags,ktimeconst,kprecis,kfreqtol,kppsfreq,kppsstab,kppsjitter,kppscalibdur,kppscalibs,kppsjitexc,kppsstbexc,kppscaliberrs"

l_sysstats="ss_uptime,ss_numctlreq"

l_sysstats2="ss_reset_r,ss_received_r,ss_thisver_r,ss_oldver_r,ss_badformat_r,ss_badauth_r,ss_declined_r,ss_restricted_r,ss_limited_r,ss_kodsent_r,ss_processed_r,ss_reset,ss_received,ss_thisver,ss_oldver,ss_badformat,ss_badauth,ss_declined,ss_restricted,ss_limited,ss_kodsent,ss_processed"

l_monstats="mru_enabled,mru_hashslots,mru_depth,mru_deepest,mru_maxdepth,mru_mindepth,mru_maxage,mru_minage,mru_mem,mru_maxmem,mru_exists,mru_new,mru_recycleold,mru_recyclefull,mru_none,mru_oldest_age"

l_authinfo="authreset,authkeys,authfreek,authklookups,authknotfound,authencrypts,authdigestencrypts,authcmacencrypts,authdecrypts,authdigestdecrypts,authdigestfails,authcmacdecrypts,authcmacfails,authkuncached,authexpired"

l_ntsinfo="nts_client_send,nts_client_recv_good,nts_client_recv_bad,nts_server_recv_good,nts_server_recv_bad,nts_server_send,nts_cookie_make,nts_cookie_decode,nts_cookie_decode_old,nts_cookie_decode_too_old,nts_cookie_decode_error,nts_ke_probes_good,nts_ke_probes_bad,nts_ke_serves_good,nts_ke_serves_bad"

l_iostats="iostats_reset,total_rbuf,free_rbuf,used_rbuf,rbuf_lowater,io_dropped,io_ignored,io_received,io_sent,io_sendfailed,io_wakeups,io_goodwakeups,

l_timerstats="timerstats_reset,timer_overruns,timer_xmts"

I have two separate lists for sysstats atm because I have them processed
through different handlers. which would get worse if I did packets/s
columns.

More likely I could add another merge request to get ignored
for the duration. Also the list id for a recent git version.
1.2.0 lacks the *_r variables from sysstats.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20210311/d7397afd/attachment.htm>