| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
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@
|
|
|
|
|
|
diff from Maurice Janssen. Manpage help from jmc and Maurice, other nits
from deraadt and otto.
ok deraadt, otto
|
|
|
|
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
|
|
do not have more than one dns request outstanding per peer. resolves
slow recovery when resolving fails initially, without clogging the
pipe with lots of dns requests; tested by Jason George; ok deraadt@
|
|
|
|
but this might increase portability since some other systems do not
grok negative tv_usec well. ok henning@
|
|
improves sensor timekeeping significantly.
Before this patch my test system's frequency adjustment would range
between -350 and +250, with timedelta rarely getting close to 0. After,
frequency adjustmens is on the order of +/- 0.05ppm, with time +/- a
few microseconds away from 0
ok henning, mbalmer, otto
|
|
signal "connection closed" upstream.
spotted by Valentin Kozamernik <tin@komna.com>
|
|
after release we should revisit this issue, we can probably safely shrink
the max imsg size.
Valentin Kozamernik in PR5401
|
|
|
|
|
|
With this patch, we give up without bothering sysctl
kern_sensors.c::sensor_find() unless we know for sure that timedelta
sensor is present.
From: "Constantine A. Murenin" <cnst+openbsd@bugmail.mojo.ru>
|
|
symbol, follow the guidelines from K&R: only one definition of a
global symbol (and possibly more declarations). Rename some vars
here and there to avoid shadowing. ok henning@
|
|
when we adjust time. This prevents ntpd from going wild when using
sensor time sources; ok henning@ (on an earlier version) and a LOT
of testing by naddy@
|
|
to ntp offsets; also, rewrite the expression to make it more clear
with no change in semantics. ok henning@
|
|
|
|
|
|
last_sensor_scan == 0. monotime might be very close to 0 after boot.
source unknown, maybe from naddy, rediscovered & ok mblamer
|
|
|
|
of the last sensor update time got broken, doesn't show up with gps since
it updates often (more often than we read), but naddy ran into it with dcf.
record time of last sensor datum seperately. ok naddy balmer
|
|
time, and make ntpd use that to send the next uery to an ntp peer and the
like. this has the advantage that changes to the clock do not interfere
with the intervals. for example, when we start on machines without an
RTC and the initial settime (-s) kicks in, intervals were strange.
idea from amandal@entrisphere.com, this implementation by me
tested ckuethe, phessler, mbalmer, ok mbalmer
|
|
them only every 30 seconds. now query them every 5,and take the median
value from 7 queries as sensor value. this takes outliers out of the
equation and makes the overall result much better, especially for
sensors with heavy jitter (like nmea for now)
|
|
From: amandal@entrisphere.com
|
|
-1 because of error, it may still participate in poll()
causing poll() to repeatedly wake up on error fd.
so make sure w edon't add -1 fds to pollevents to avoid unnecessary wakeups
From: amandal@entrisphere.com
|
|
From: amandal@entrisphere.com
|
|
too. from amandal@entrisphere.com
|
|
servers never update the system clock
|
|
takes the offset it adjtime() is already correcting for into account
when taking the offset from a sensor, we need to correct it by the
offset between system time and ntpd view.
|
