pt out by Alexander v Gernler

don't query outliers more often than any other server.  ok henning@

threshold. spotted by Constantine Murenin <mureninc@gmail.com>, mickey ok

returns NULL, we don't need loooong explanations, but at least some indicator
what went wrong, From: Michael Knudsen <e@molioner.dk>

ok henning@

them when in debug mode; ok henning@

poll interval;  ok henning@

ok henning@

fallout from the deferred dns lookups
noticed by dhartmei@

ntp_settime() -> priv_settime()
ntp_host_dns() -> priv_host_dns()

From: Joerg Sonnenberger <joerg@britannica.bec.de>

ok henning@

from otto and myself; prodded by henning;

easier on portable.  ok henning@

anymore, same thing for us and it makes darren's life easier for the
portable

precision field when we reply in server mode accordingly. from phessler

plus one

inherit rootdelay from the delay from the last client update from the peer
that we picked last time to adjust the local clock.
in some cases we use the average offset between two peers' client updates,
then use the average delay between the two as well.

and such

code path for NTP4 remains unchanged, we already set refid correctly there.
NTP3 and older uses an IPv4 address as refid.
use the IP of the server we last synced to if it was a IPv4 one.
sometimes we use the average offset between two, in that case just pick
one for the IP.
this scheme naturally fails when we query IPv6 servers and have to reply
to IPv4 NTP3 (or even older NTP versions) clients - refid stays at 0 then.
this is a protocol limitation, nothing we can do about it.

might have become invalid (because the peer showed up, dns request sent to
parent, peer vanishes, and then the reply comes back), so do not fatal() in
that case but just log_warnx(). provoked by brad