On Fri, Jun 8, 2012 at 12:17 AM, Brian Utterback <brian.utterb...@oracle.com> wrote: > On 6/7/2012 7:35 PM, Dave Hart wrote: >> >> On Thu, Jun 7, 2012 at 10:47 PM, Brian Utterback >> <brian.utterb...@oracle.com> wrote: >>> >>> (Some day it would be nice if "mrv&0&9" worked the way you expected, but >>> >>> would you believe "rv 0" and "rv anything-else" call entirely different >>> functions? ) >> >> "rv 0" means system variables. >> >> "rv&0" is not defined -- ampersand shorthand for association IDs start >> with&1. >> >> >> FYI, older versions of ntpq require lpeers, lassoc, or similar before >> & references work. Newer ones (including 4.2.6 I believe) always >> support& references and will silently first issue lassoc to learn the >> association IDs if needed. > > Quite. I meant "rv 0". My point is that I would really like "mrv &0 &99" to > pretty much do "rv 0" followed in turn by each of the "rv associd" choices. > I guess you are just pointing out that they are kind of different?
Right. "rv" takes an association ID. 0 is reserved special case of systemwide variables, any other number indicates variables specific to the given association number. &0 and 0 are not synonymous here. &0 would mean the zeroeth association ID known to the server, but & references count like humans starting at 1. So IMO &0 should complain, though one could redefine it to be a long way of writing 0. Cheers, Dave Hart _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions
