spotted the hard way by theo on armish, pinned to this changed by me.
no cookie for ckuethe for not testing on machines with bad clocks.

Make the imsg protocol network-safe.
it might be network safe, but half the imsg based daemons on my firewalls
dont run anymore.

Currently the receiver fetches an imsg via imsg_get() and if he expects
an fd, he then calls imsg_get_fd() to fetch the next fd queued on the
imsgbuf from which the imsg came.
This changes hides the fd queueing mechanism to the API user.  When closing
an imsg with an fd, the message is flagged so that the receiving end knows
it must dequeue the fd in imsg_get() and return it with the imsg structure.
This way there is no (less) possible screw up from imsg_get_fd() not being
called directly after imsg_get() by the user. The retreived imsg is
self-contained.
ok pyr@, "I like that" henning@

ok pyr@

add a flag field, use u_int32_t for pid_t and extend type to 32 bits
for padding.
ok pyr@

time corrections. Once the clock is synced again, start computing a fresh
frequency correction.
ok henning

corrections more often. Due to physical effects crystal oscillators aren't
really stable beyond 1000s or so - at least not the kind found in pc's.
ok henning

behavior change.
ok eric@

offset. This avoids future frequency adjustments based on measurements of a
clock that was being adjusted. End result: more stable clock and better
frequency convergence.
Also, fix a mis-ordered structure member while I'm here.
ok henning

i remember we already had the confusion and bgpd doesn't have the endpwent

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@