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

empty while in the -s period, so the poll timeout actually times out
if there are no interfaces available. ok henning@

from a long time ago. ok ckuethe@

it with a simple filter in the yylex() loop.
The compression in lgetc() didn't happen for quoted strings,
thus creating a regression when tabs were used in variables.
Some testing by todd@ and pyr@
OK deraadt@

ok henning@

Requested and OK deraadt@

expand to space or tab, and a \ followed by newline should be ignored
(as a line continuation).  compatible with the needs of hoststated
(which has the most strict quoted string requirements), and ifstated
(where one commonly does line continuations in strings).
pointed out by mpf, discussed with pyr

happens when a SIGINFO is received, or when the majority of peers or
sensors is bad. The latter with a maximum of once per 24 hour.
ok henning@ ckuethe@ mbalmer@

yylex implementation and the code which interacts with yylex.  this also
brings the future potential for include support to all of the parsers.
in the future please do not silly modifications to one of these files
without checking if you are de-unifying the code.
checked by developers in all these areas.

as found in hoststated, and make all the code diff as clean as possible. a
few issues remain mostly surrounding include support, which will likely be
added to more of the grammers soon.
ok norby pyr, others

ok beck

the configuration file.
"yes please, ok" henning@

negative parameters.  extend lex to spot numbers in the stream.  as well,
make it easier to add parameters on command line in any order later
ok otto ckuethe

priority.
ok gwk, mbalmer, weingart
"explicit non-ok from" henning

sensors is requested, but no sensors are found.
ok henning

instead of kind-of manual copyin/out. increases accuracy in server mode.
collecting dust in my tree for some time, result of a conversation with
somebody i really want to give credit to, but I can't find the mails now :(
okey dokey sez theo