| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2009-05-13 | when using a timedelta sensor for -s, if the sensor is invalid during | Kevin Steves | |
| 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@ | |||
| 2009-02-08 | spelling in comment | Kevin Steves | |
| 2009-01-27 | fix printf format specification to print max len 4 for refid, | Kevin Steves | |
| which may not be null terminated; ok henning@ | |||
| 2009-01-26 | return the correct refid for a sensor; ok henning@ | Christian Weisgerber | |
| 2008-06-10 | According to the latest SNTPv4 spec in RFC4330, secondary servers | Christian Weisgerber | |
| return the address of the synchronization source as reference identification. Remove the obsolete special casing specified in RFC2030. ok henning@ | |||
| 2008-06-09 | rename refstr to refid since it is an int32; ok henning | Theo de Raadt | |
| 2008-06-09 | do not copy up to two garbage characters from a 1 char string into a 4 char | Theo de Raadt | |
| output buffer; ok henning | |||
| 2008-06-09 | spacing | Theo de Raadt | |
| 2008-06-09 | Allow outgoing replies from sensor-driven servers to have a | Chris Kuethe | |
| user-configurable reference ID, eg. "GPS" or "DCF"... ok mbalmer | |||
| 2008-03-02 | set the refid for v4 queries too. this allows sensor-driven ntpd to says its | Chris Kuethe | |
| reference is "HARD" (or "GPS", "UMBG", "UDCF" ... in theory) rather than "^@^@^@^@" "why not" henning@ | |||
| 2007-09-12 | Add a knob to compensate for a refclock that is early or late. Based on a | Chris Kuethe | |
| diff from Maurice Janssen. Manpage help from jmc and Maurice, other nits from deraadt and otto. ok deraadt, otto | |||
| 2007-08-04 | This diff makes ntpd poll for sensors more aggressively when the use of | Chris Kuethe | |
| sensors is requested, but no sensors are found. ok henning | |||
| 2007-01-23 | Typo in fatal() message found by dunceor @ gmail dot com | Claudio Jeker | |
| 2007-01-15 | the new sensors tre can give us the number of sensors per type. | Henning Brauer | |
| 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> | |||
| 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 | Add some comments on the expresssion which converts sensor timedeltas | Otto Moerbeek | |
| to ntp offsets; also, rewrite the expression to make it more clear with no change in semantics. ok henning@ | |||
| 2006-12-28 | forgot a dereference in the previous conversion; ok deraadt@ | Christian Weisgerber | |
| 2006-12-23 | adapt to new two-level sensor sysctl framework; by Constantine A. Murenin | Theo de Raadt | |
| 2006-11-20 | with usig the meadian offset froma number of measurements the recording | Henning Brauer | |
| 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 | |||
| 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-12 | need to call adjtime once in a while here too, otherwise sensor-only | Henning Brauer | |
| servers never update the system clock | |||
| 2006-10-12 | internally, ntpd doesn't work with absolute offsets to system time, but | Henning Brauer | |
| 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. | |||
| 2006-08-19 | make sure updates from sensors have the "synced" flag set | Henning Brauer | |
| 2006-06-30 | spaces | Theo de Raadt | |
| 2006-06-02 | just ise "HARD" as refid with sensors for v3 clients | Henning Brauer | |
| 2006-06-01 | urgs, other stuff snuck in | Henning Brauer | |
| 2006-06-01 | do not use /dev/hotplug for now, only one reader supported yet | Henning Brauer | |
| 2006-05-29 | when we cannot open /dev/hotplug, donn't bail, just work without | Henning Brauer | |
| with ckuethe | |||
| 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 | get clock src id from the timedelta sensor desc. | Henning Brauer | |
| unfortunately I still don't have any hardware to test this ;( | |||
| 2006-05-28 | if sysctl gives ENOENT the sensor is gone and we remove it | Henning Brauer | |
| 2006-05-28 | let sensor_query handle removals itself | Henning Brauer | |
| 2006-05-28 | sensor_byid not needed any more | Henning Brauer | |
| 2006-05-28 | hotplug devid will go away in a minute, so don't use it here any longer | Henning Brauer | |
| 2006-05-28 | do not bother with rmeoval events, we remove sensors whoch vanished or | Henning Brauer | |
| are not a timedelta sensor any more on query on the fly anyway | |||
| 2006-05-28 | DV_SENSORS is no more, plug workaround for the time to the real solution | Henning Brauer | |
| 2006-05-28 | make use of the new hotplug events for sensors showing up or vanishing | Henning Brauer | |
| 2006-05-27 | add sensor_byid(), return sensor by its id | Henning Brauer | |
| 2006-05-27 | stop passing the config around all time, just store one copy | Henning Brauer | |
| 2006-05-27 | factor out sensor_probe from sensor_scan so we can probe a sensors when | Henning Brauer | |
| we know its idea without scanning all again | |||
| 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 | config file bits for timedelta sensors, so one can specify which devices | Henning Brauer | |
| to use. "sensors *" just uses all. untested due to lack of hardware. hacked on the road somewhere between vancouver and calgary | |||
| 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 | |||
 |
index : src | |
| OpenBSD base system |
| summaryrefslogtreecommitdiff |