| Age | Commit message (Collapse) | Author |
|---|
|
getcap->cgetent. pwcache->user_from_uid. And then repair references.
ok jmc
|
|
value < 0. errno is only updated in this case. Change all (most?)
callers of syscalls to follow this better, and let's see if this strictness
helps us in the future.
|
|
which effectively caused the config file to be ignored. So move
parse_config() back after create().
OK deraadt@
|
|
From Anton Borowka.
ok sthen
|
|
Change distance sensor type to be displayed as meters with 3 decimals
instead of millimeters.
ok mpi@ kettenis@
|
|
"/" for 'x' so that scripts can be run anywhere in the filesystem
(intended behaviour). The latter may seem very permissive, but it is
less permissive than "rwxc" ....
ok mestre, a while back
|
|
|
|
defining the terms "sensor" and "alert", avoiding fuzzy wording
like "reporting period" and "state dumping", explaining how Boolean
values are represented and that ranges are inclusive, and mentioning
the syslog facility used. Also add relevant cross references and
drop irrelevant ones.
OK jmc@
|
|
from Matthias Pitzl
|
|
ok deraadt@
|
|
|
|
|
|
|
|
ok jmc@
|
|
do it in the caller.
|
|
|
|
possible. Annotate <sys/param.h> lines with their current reasons. Switch
to PATH_MAX, NGROUPS_MAX, HOST_NAME_MAX+1, LOGIN_NAME_MAX, etc. Change
MIN() and MAX() to local definitions of MINIMUM() and MAXIMUM() where
sensible to avoid pulling in the pollution. These are the files confirmed
through binary verification.
ok guenther, millert, doug (helped with the verification protocol)
|
|
drive reporting too. OK jsing@
|
|
<sys/sysctl.h> will pull in the universe (I am working on breaking that
assumption in a gentle fashion)
|
|
- Pressure (10^-3 Pa)
- distance (10^-6 m)
- acceleration (10^-6 m/s^2)
ok deraadt@ reyk@
|
|
and make it compatible with bsd.lv mandoc and with groff-1.21.
This tweak was originally added for compatibility with groff-1.15,
which is no longer needed.
ok jmc@ kristaps@
|
|
|
|
- change accuracy of SENSOR_FREQ from Hz to muHz
- add SENSOR_VOLTS_AC entry to userland programs
ok deraadt@
|
|
|
|
by returning ENXIO instead of ENOENT, to essentially indicate hotplug
sensor that has gone away. Accessing beyond the end of the sensordev
list still returns ENOENT, so that you can see there are no further devices.
ok kettenis oga
|
|
|
|
the logic of which assumes that there is at least one sdlim.
ok henning
|
|
instead of reloading the configuration for all sensordevs.
ok henning
|
|
hotplugging.
* Factor out some code from main() into a new create() procedure, to save
some memory and make the code tidier.
ok henning
|
|
deferred thread, as well as some timedelta sensors).
ok henning, ckuethe
|
|
option parsing. Found out the hard way by jdixon on ifstated.
ok sobrado@, jdixon@, millert@
|
|
double to int64_t conversions happen sooner rather than later
discussed with / ok by kettenis
|
|
|
|
that the time always goes forward, so reports are neither duplicated nor lost.
Report state changes stabilised through dampening immediately, instead of delay-
ing them until the next reporting window; previously, it was common for check()
to lag one second behind report(), hence the initial report was delayed one
extra minute (this then reduces the number of sleep(3)/nanosleep(2) calls, too).
ok ckuethe; some man-page suggestions jmc
|
|
ckuethe@
|
|
- it doesn;t make sense to list esm(4) in SEE ALSO
|
|
without regard for the specific value. It's a big heavy binary hammer...
ok & style feedback from cnst
|
|
ok mbalmer
|
|
you might want to toggle an error light when a sensor is not OK. Perhaps
you might want to schedule a shutdown if a sensor is reporting bad news.
Now you can do this, and cancel that pending shutdown (or turn off the error
light) if the sensor decides all is well.
ok mbalmer (who came up with an almost identical diff months ago)
useful feedback and generally positive responses from deraadt, henning, msf
|
|
partly spotted by bluhm@ grunk@; ok grunk@
|
|
|
|
|
|
document how values are parsed in sensorsd.conf(5).
ok deraadt@; man-page ok/help jmc@
|
|
the impression that alerts are only issued when things go wrong, not when they
come back to specification -- but this was never the case with sensorsd.
Whilst here, also zip some useless examples, as we now have so many.
Discussed with jmc@
|
|
mechanism; ok jmc@ henning@
|
|
even if it is present in certain dictionaries (it is). Also, it doesn't add
that much to .Nd anyhow. Requested by jmc@
|
|
fix description of when the command is executed (it was wrong from the start);
say a few more words about automatic monitoring of all sensors that keep state.
ok henning@
|
|
* add myself to the copyright; remove unneeded synopsis
* invalid sensors can now be monitored as such (since c2k7)
* manual boundaries for smart sensors are no longer ignored (since c2k7)
* populate history with 4.1 and 4.2 additions
* add caveats section documenting a long-standing misconception and a workaround
some help jmc@; ok jmc@
|
|
|
|
|
