| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
krw running my diagnostics
|
|
Improves support for both 'smart' (those providing sensor status) and
'old-style' sensors.
Due to re-design, the following improvements are now present and many
flaws are now gone:
== for smart sensors ==
* automatically monitor all sensors that provide status by themselves,
with the possibility to ignore certain individual sensors or sensors
of certain type (appropriate template for sensorsd.conf is included)
* report actual sensor status as provided by the driver. Previously,
WARN, CRITICAL and UNKNOWN statuses were considered the same, but
now they are different and will be reported separately. This also
improves readability of the log-files and consistency with sysctl
output.
* ability to ignore status provided by the driver with the 'istatus'
keyword ("ignore automatic status" or "I set the status"), with the
possibility to set your own settings for acceptable limits.
Previously, it was not possible to set any kind of user limits for
those sensors that had their own status facilities.
== for old-style sensors ==
* previously, lm(4)-style fans that were flagged SENSOR_FINVALID during
sensorsd startup were completely ignored, but now their invalid status
is appropriately reported, and they are monitored again when they come
out of their invalid mode
* previously, a sensor that had an empty entry in the configuration file
was reported to be "within limits", but now it will not be monitored
at all (unless, of cause, it provides its own status)
As a bonus, sensorsd syslog entries should now be shorter, and the
majority of them will fit on one line on 80-column terminals.
ok beck@, henning@, deraadt@
|
|
|
|
complete sysctl name does not yield anything; ok henning, otto
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
prompted by/ok dlg@ deraadt@
|
|
|
|
|
|
grudgingly ok deraadt@
|
|
ok and prodding @jmc
|
|
- update paths for 3{F,f,P,p}
ok espie millert steven
|
|
and matches "zcat" (as opposed to uncompress -c");
grammar tweak whilst here too;
ok millert
|
|
man(1) searches, as well as from the numerical sections list, as they do
not exist
- remove the {contrib,new,old} sections, as they point to directories
that do not exist
- make the X11 section an alias for the X11R6 section (instead of
pointing to a non-existent directory)
ok millert
|
|
|
|
|
|
|
|
remove it (updating it makes little sense);
ok millert
|
|
plenty ok
|
|
remove comments that said otherwise.
"I agree" deraadt@;
"diff looks fine" dlg@;
ok henning@, beck@.
|
|
|
|
(this decreases build time a bit too)
ok todd (and i assume legacy-architecture-miod would not object either)
|
|
okay xsa, sobrado, jdixon
|
|
variables from arch/sh/ to arch/landisk/. ok deraadt@
|
|
okay deraadt@
|
|
|
|
/etc/*.if files.
okay reyk@, deraadt@, krw@...
|
|
"why not" mblamer@, ok krw@ todd@
|
|
in /etc/fstab instead of using some weird homegrown scripts.
No support for boot time mounting yet, so "noauto" is still needed.
original idea from david@
help and discussion todd@ bluhm@ beck@, manpage help jmc@
ok simon@ tedu@ bluhm@ todd@, "looks good" thib@
|
|
|
|
|
|
rule needs an explicit "inet" to match on IPv4 addresses only. OK henning@
|
|
|
|
pick one as per default.
ok claudio@
|
|
receivers can cold start in the time it takes the boot process to get
close to starting ntpd. Even if the gps is not ready or the fix is not
valid, at least the sensor has been created; ntpd won't have to wait
a few minutes before scanning for the sensor. This makes using GPS as
the sole source of time a bit easier.
ok deraadt
|
|
|
|
|
|
Feedback from drahn@, millert@, marco@. "then get it in" deraadt@.
|
|
|
|
|
|
This adds an HMAC protected synchronization protocol for use by spamd and
spamlogd.
- spamd can receive updates from other hosts for GREY, WHITE, and TRAPPED db
entries, and will update the local /var/db/spamd accordingly.
- spamd can send updates when it makes changes to the GREY or TRAPPED
entries in the db to other hosts running spamd. (Note it does not send
WHITE entries because the other spamd will see the GREY changes and have
complete information to make appropritate decisions)
- spamlogd can send updates for WHITE db entries that it performs on the local
db to other hosts running spamd, which will then apply them on remote hosts.
note that while this diff provides synchronization for changes made to the
spamd db by the daemons, it does *not* provide for sychonizing changes
to the spamd db made manually with the spamdb command.
Synchronization protocol and most of the work by reyk@,
with a bunch of the spamd, and spamlogd stuff by me.
testing mostly at the U of A, running happily there under big load.
ok reyk@ jmc@
|
