On Wed, Aug 21, 2019 at 1:48 PM Miroslav Lichvar wrote:
> But how should this work in chronyc? When should it resolve names from
> addresses and when should it request/send hostnames? This could be
> very confusing and/or break compatibility with existing scripts/use
> cases.
I can only imagine
On Wed, Aug 21, 2019 at 01:35:10PM +0200, Nuno Gonçalves wrote:
> Maybe a dual null terminated c-string where current protocol clients
> would stop on the first null?
>
> I'm throwing this without checking the actual protocol...
Currently, there are no strings in the protocol. Everything is
Maybe a dual null terminated c-string where current protocol clients
would stop on the first null?
I'm throwing this without checking the actual protocol...
Thanks,
Nuno
On Wed, Aug 21, 2019 at 12:55 PM Miroslav Lichvar wrote:
>
> On Wed, Aug 21, 2019 at 12:31:55PM +0200, Nuno Gonçalves wrote:
On Wed, Aug 21, 2019 at 12:31:55PM +0200, Nuno Gonçalves wrote:
> I would like to be able to identify from chronyc sources/sourcestats
> the corresponding server on the configuration file.
>
> Currently I can only obtain the IP address or the reverse DNS lookup.
>
> Could it fit in the runtime
I would like to be able to identify from chronyc sources/sourcestats
the corresponding server on the configuration file.
Currently I can only obtain the IP address or the reverse DNS lookup.
Could it fit in the runtime structure/monitoring protocol a additional
field for either the original DNS
