up causes overcompensation and confusing debug log entries; noticed
by dtucker@

henning@

ok henning@ ckuethe@

more than one token MUST be put in parentheses!

only do frequency compensation if the clock is synced, and a slightly
diffent way of computing the linear regression.
You'll need a recent kernel and libc to use this.
Testing by naddy@ and ckuethe@ and others, thanks!
ok henning@

ok henning@

overcompensating. From DragonFly, uses recent adjtime(2) changes,
so you'll need a recent kernel. ok henning@

ok henning@

ULONG_MAX does not work; the max upper bound is LONG_MAX,
since LONG_MAX == LLONG_MAX on 64bit archs. ok deraadt@ henning@

it will wait until the next poll.
ok henning@

from henning and myself

with ckuethe

weight timedelta sensors higher than ntp peers, for example
ok deraadt mbalmer

unfortunately I still don't have any hardware to test this ;(

are not a timedelta sensor any more on query on the fly anyway

we know its idea without scanning all again

new sensors showing up will be announced that way when slacking ml comes
back from food

to use. "sensors *" just uses all. untested due to lack of hardware.
hacked on the road somewhere between vancouver and calgary

other things work.  ok henning

now. untested due to lack of hardware, and it wouldn't have worked in the
plane anyways. work in progress, currently picks up and uses all sensors
it finds, config file bits to be added soon. theo fine with this going in

make priv_adjtime() deal with offsets, not peers.

first bits from a way to long flight

suggested by "Karsten W. Rohrbach" <karsten@rohrbach.de>

openwall.com, ok henning@