| Re: [chrony-dev] preparing for 1.25-pre1 |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
On Tue, Feb 01, 2011 at 09:55:09PM -0600, John Hasler wrote:
> > What if we started using <linux/ioctl.h> instead of maintaining our
> > own copy of the ioctl macros for every arch?
>
> Good idea. It appears that they are standardizing those macros anyway.
Ok, I'll look into it.
> > Is this about the tracking output? Reference ID is always 32 bits and
> > is equal to the source's IP address only for IPv4...
>
> It's confusing as it always has been the source's IP and the dotted-quad
> notation makes it look like a valid IPv4 address even when IPv6 is in
> use.
chronyc always printed both, refid and name/address in parentheses. The
address is normally resolved to a name, but with -n and IPv4 there
are two equal quad-dotted values. There are also some special values,
refid is 127.127.1.0 with local stratum and 0.0.0.0 when not
synchronized.
As ntpd uses the same notation I'd be in favor if keeping it, maybe
just better explain it in the documentation.
> > But chronyc knows both refid and IP address (and if it's IPv4 or
> > IPv6)...
>
> How?
The tracking report has
uint32_t ref_id;
IPAddr ip_addr;
ip_addr.addr is a union for 32 and 128-bit values and ip_addr.family
is IPADDR_INET4 for IPv4, IPADDR_INET6 for IPv6 and IPADDR_UNSPEC with
a reference clock (and instead of address in the tracking output the
refid is printed as string).
--
Miroslav Lichvar
---
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.