Age | Commit message (Collapse) | Author | |
---|---|---|---|
2007-01-15 | Although Unix compilers accept more than one definition of a global | Otto Moerbeek | |
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@ | |||
2007-01-14 | Esape from the Mouth of Madness by adjusting stored sensor offsets | Otto Moerbeek | |
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@ | |||
2006-12-20 | let ntpd use sensors immediately after system boot by special casing | Henning Brauer | |
last_sensor_scan == 0. monotime might be very close to 0 after boot. source unknown, maybe from naddy, rediscovered & ok mblamer | |||
2006-11-30 | Allow sensors in a sensors-only configuration to set the time at startup. | Chris Kuethe | |
2006-10-27 | use clock_gettime(CLOCK_MONOTONIC, ..) to get a monotonically increasing | Henning Brauer | |
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 | |||
2006-10-24 | timedelta sensors are usually updated very often, but we used to query | Henning Brauer | |
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) | |||
2006-10-21 | Found that even if client fd (i.e to NTP source) is set to | Henning Brauer | |
-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 | |||
2006-07-01 | remove some unneeded includes; one found by vetinari | Otto Moerbeek | |
2006-06-30 | spaces | Theo de Raadt | |
2006-06-26 | increase polling intervbal, but only after we are synced and have done | Otto Moerbeek | |
a few frequency adjustments. ok henning@ | |||
2006-06-21 | avoid a race by installing SIGCHLD handler before fork() is called. | Otto Moerbeek | |
ok henning@ ckuethe@ | |||
2006-06-17 | Import frequency conrrection code from dragonfly, whith some changes: | Otto Moerbeek | |
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@ | |||
2006-06-09 | set session id and init logging in -s mode. tested by david@ and matthieu@; | Otto Moerbeek | |
ok henning@ | |||
2006-06-08 | simplify; ok henning@ | Otto Moerbeek | |
2006-06-07 | Compensate old offsets with the amount of adjustment done, avoiding | Otto Moerbeek | |
overcompensating. From DragonFly, uses recent adjtime(2) changes, so you'll need a recent kernel. ok henning@ | |||
2006-06-04 | Only invalidate stored replies if an adjustment was really made. | Otto Moerbeek | |
ok henning@ | |||
2006-06-02 | incredibly stupid typo | Henning Brauer | |
2006-06-01 | When expanding servers, do not forget to copy weight. ok henning@ | Otto Moerbeek | |
2006-06-01 | urgs, other stuff snuck in | Henning Brauer | |
2006-06-01 | put back regular sensors scanning | Henning Brauer | |
2006-05-31 | only actually run sensor_query when it is due, not every time poll returns | Henning Brauer | |
2006-05-28 | allow for weight to be added to sensors or servers, so that one can | Henning Brauer | |
weight timedelta sensors higher than ntp peers, for example ok deraadt mbalmer | |||
2006-05-28 | let sensor_query handle removals itself | Henning Brauer | |
2006-05-28 | DV_SENSORS is no more, plug workaround for the time to the real solution | Henning Brauer | |
2006-05-27 | stop passing the config around all time, just store one copy | Henning Brauer | |
2006-05-27 | make ntpd listen on the hotplug socket and decode yadda yadda, because | Henning Brauer | |
new sensors showing up will be announced that way when slacking ml comes back from food | |||
2006-05-27 | scan for new timedelta sensors every five minutes for now, ok deraadt | Henning Brauer | |
2006-05-26 | add support for timedelta sensors, which pretty much means udcf(4) right | Henning Brauer | |
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 | |||
2006-05-25 | more bits from transatlanic flight: | Henning Brauer | |
make priv_adjtime() deal with offsets, not peers. | |||
2006-05-25 | figure out the refid to send to NTP v3 clients early and store it | Henning Brauer | |
first bits from a way to long flight | |||
2006-05-14 | PFD_MAX betterer than harcoded 1 | Henning Brauer | |
2005-08-10 | Propogate server's leap indicator flags to clients; ok henning@ | Darren Tucker | |
2005-08-08 | with -s, do not wait if we don't have any peers at all. | Henning Brauer | |
From: Thomas Jarosch <thomas.jarosch@intra2net.com> | |||
2005-07-15 | remove recently added "using privsep user X" message, spams console in -s | Henning Brauer | |
mode, noticed by kettenis | |||
2005-07-15 | fix a function name in an error message | Henning Brauer | |
why this was rotting in my tree for so long, I dunno - and I dunno where it came from | |||
2005-07-11 | Print privsep user and dir when in debug mode; ok henning@ | Darren Tucker | |
2005-07-05 | Save transmit time for each peer for later use as refid for SNTPv4 | Darren Tucker | |
replies. ok henning@ | |||
2005-06-19 | use a little state engine to keep track of delayed dns lookups and such, | Henning Brauer | |
eases things tested by Jason Ackley <jason@ackley.net> Matthias Kilian <kili@outback.escape.de> Stephen Marley <stephen@marley.org.uk> sturm@ theo ok | |||
2005-05-26 | Ensure previous adjust has completed before clearing alarm flag; ok henning@ | Darren Tucker | |
2005-05-23 | no need for endpwent(0 here either | Henning Brauer | |
2005-05-03 | setres[ug]id; ok deraadt@ | Damien Miller | |
2005-04-18 | correctness: only account for offset after settime in next and deadline | Henning Brauer | |
when those timers are actually running. due to the way ntpd's logic works this does not really make a difference, but correctness is good. spotted by me, joerg agrees | |||
2005-04-18 | after setting the clock hard correct the "next" and "deadline" timestamps | Henning Brauer | |
by the offset From: Joerg Sonnenberger <joerg@britannica.bec.de> | |||
2005-03-24 | one more fatal/fatalx, alexander | Henning Brauer | |
2005-03-08 | when trying short-circuit the wait for the first reply for -s, only | Henning Brauer | |
do so when -we tried to send at least one query (that is the change) -we could not send ou a single one without failure (this was already in place but catched too much) problem independently noticed by nick and danh, ok mickey danh, testing by many | |||
2005-03-08 | knf | Theo de Raadt | |
2005-03-08 | missing break spotted by lint | Theo de Raadt | |
2005-02-22 | when sending a query already returns a failure, we're not going to see | Henning Brauer | |
a reply to that query. if we get errors for all queries and the initial settime() is still due and thus the parent process still waits (not yet daemonized!), send an IMSG_SETTIME with offset 0. shortens the delay dramatically when you boot without network idea from a discussion with theo | |||
2005-02-02 | KNF | Henning Brauer | |
2005-01-28 | Simplify interval scaling and randomize query intervals; ok henning@ | Darren Tucker | |