reply instead of doing it in ntpd itself by getting the time we read
from the socket. based on a diff from mickey hacked in shape by me,
lots of testing and review from ckuethe and sthen, theo and claudio like it
too

junk. from thorsten glaser.

"fine by me. it's maybe not ideal, but it's better" jmc@

the first query we will never do the settime because
SENSOR_QUERY_INTERVAL (30s) is greater than SETTIME_TIMEOUT (15s).  so
during the settime period only, be more aggressive and use
SETTIME_TIMEOUT/3 for the query interval.
ok henning@

input & ok theo

allocations fails.
looks right deraadt, krw
ok henning

Don't log kiss code for now.

ok henning@, 'I think I agree' otto@

ok henning@

ok henning@ jmc@

corrupt contents. ok henning@

which may not be null terminated; ok henning@

found on this laptops harddisk, probably from stockholm

to start the for loop and not 1 which was correct long long time ago.
OK otto@ found by Anirban Sinha ASinha(at)zeugmasystems.com

to some stupid ipv6 bug in particular), remove that 'listen' from the list
and continue operation.  issue spotted by naddy
ok henning

which only works in w.europe
- use a more realistic value for udcf correction example
- use a GPS-only receiver for "refid GPS" example
suggested/ok mbalmer

the offset since we use monotime for these for some time now, and monotime
is not affected by system time changes (like, duh, that was the reason for
the change). PR5927

event. so don't use the word "before" .. and leave the mention ambigious
ok henning

reason: the parent process must never ever block, but the dns routines can.
last not least this fixes ntpd -s 'hanging' for a long time.
tested by a couple of people

Diff from Gleydson Soares gsoares (at) gmail (dot) com
OK henning@

address as ref ID (RFC4330).  ok henning@

return the address of the synchronization source as reference
identification.  Remove the obsolete special casing specified in RFC2030.
ok henning@

output buffer; ok henning

user-configurable reference ID, eg. "GPS" or "DCF"...
ok mbalmer

comments & ok henning@

offset. The 180s limit doesn't help very much these days.
ok otto@ mbalmer@

Use arc4random_uniform() when the desired random number upper bound
is not a power of two
ok deraadt@ millert@

reference is "HARD" (or "GPS", "UMBG", "UDCF" ... in theory) rather than
"^@^@^@^@"
"why not" henning@

but only do the final popfile call after yyparse() is done.
This also fixes config reload on SIGHUP for some daemons.
Spotted by otto@. OK deraadt@

This allows recovery after an IP address change (e.g. on dialup links).
Also move the update of "nextaction" timeout below the deadline check.
OK henning@

because otherwise the poll timeout will stay at SETTIME_TIMEOUT (15s)
forever unless we time out waiting for the first reply with -s
spotted by Aaron Riekenberg <aaron.riekenberg@gmail.com>

also add "(no drift file)" to the adjfreq log message on failure;
ok henning@

based on an initial diff from Simon Kuhnle,
and input from Joerg Sonnenberger;
ok otto