a reply to that query.
if we get errors for all queries and the initial settime() is still due
and thus the parent process still waits (not yet daemonized!), send an
IMSG_SETTIME with offset 0.
shortens the delay dramatically when you boot without network
idea from a discussion with theo

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