| Age | Commit message (Collapse) | Author |
|---|
|
Deprecate INSTALL and DEINSTALL, write out warnings in pkg_create.
Clean up some more old cruft
|
|
|
|
able to use it in other cases.
|
|
at reconfiguration time.
|
|
bgpd uses internaly so we can just dump that one out.
Found by Stuart Henderson, OK henning@
|
|
|
|
on communities with 0 in them.
|
|
pfsync_state (as in pfctl, but in network byte order).
ok henning@ toby@ pyr@
|
|
not allow anybody to use 65535. That one is reserved for well known
communities. Add in that check again.
|
|
|
|
split the code to start the event loop in two functions.
introduce merge_config which will be used later on.
|
|
|
|
Remove two passes visitors, we don't use them.
|
|
|
|
|
|
Just do one single try {} catchall {} per-method, as this is enough.
New methods: extract_and_progress, install_and_progress, that catch
interrupts (die) deal with fake, and handle the progress meter.
One single method: mark_progress, can be used for extraction, installation
and deletion.
|
|
|
|
already installed in a hash, and do a shallow copy of the list when
necessary, using make_copy.
This removes a lot of action-at-a-distance in packing-list elements.
|
|
|
|
|
|
are registered in a hash. This will be used to create borked packages in
a much simpler way.
Also, set_pkgname, so that I don't have to remember whether this
packing-list already has a name. Useful when copying stuff over.
|
|
|
|
bigger sets)
|
|
|
|
|
|
|
|
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@
|
|
- consistent text for STANDARDS
- note which options are extensions to POSIX
|
|
ok claudio@
|
|
|
|
|
|
|
|
|
|
|
|
environment instead.
|
|
|
|
than one message.
|
|
forward IMSG_CTL_RELOAD which ends up not doing anything for now.
|
|
names that match installed packages, but still mark them to be installed,
so that they're returned as dependencies, and get updated first.
Write in TODO that the current situation is brittle, solved dependencies
should get adjusted in real time to be 100% sure this won't cause problems...
|
|
already there. of course this is a dummy for now.
|
|
interfaces and areas. With this carp setups using ospfd are more reliable
because we can fail over if the OSPF connectivity is (partially) lost.
OK norby@
|
|
ok deraadt@
|
|
|
|
usable by default, where we will monitor all sensors that automatically
provide status, and this watch_cnt won't make much sense. Besides, upon
startup, sensorsd already shows all sensors that it is going to monitor,
making this watch_cnt rather unimportant.
ok henning@
|
|
|
|
ok reyk@
|
|
for custom evaluations.
pyr agrees to put it in now but to do some improvements of the timeout
handling later.
|
|
ok jmc@
|
|
|
|
This allows us to always compute checksums based on $self->fullname,
so as a result, we no longer need to pass as many parameters around.
Small negative side-effect: the method names no longer reflect reality
well, they will need renaming at some point...
|
