libnutclient: for Mozilla NSS setup, the way to
provide an expected CERTHOST address was missing. Now the API is fixed
in this regard, at the cost of adding arguments to methods introduced in
the previous release. [issue #3331, PR #3408]
MAXCONN setting in upsd.conf: now this value is checked against the
getrlimit() (e.g. ulimit -n) setting of the operating system for this
daemon, where available, and the upsd data server would refuse to start
if the requested value is larger than what is allowed (minus some reserve
for configuration files and other use-cases). [issue #3365]
upsmon and
upssched integration: the CMDSCRIPT and NOTIFYCMD definitions were
revised for the first token to mean an exact program name (possibly with
spaces in the value), not a shell scriptlet. Documentation in earlier NUT
releases implied that arguments could be passed here — this is no longer
true. If you need to pass special arguments to a notification program,
please use additional separately quoted tokens, or write a small helper
script to do so and specify its path here. The SHUTDOWNCMD is still a
scriptlet, as far as specifying command arguments is concerned, but it also
newly supports parsing multiple tokens as additional arguments. [PR #3499]
upsd data server: If SSL configuration was provided,
but the server failed to apply some aspect of that, it should now abort
with an explanation (and not proceed with insecure start-up like it could
do before). [issue #3331, PR #3435]
Enabled support for nutauth.conf files to provide credentials and/or
SSL settings in clients which previously only did best-effort attempts at
secure communications without an individual certificate, and only anonymously
for reading like upsc.
The new -A filename option defaults to trying to use a nutauth.conf file
(if found in one of the default locations) but not failing if one is not
usable; specific values can require use of such a file or to not even try
reading one (none as the legacy default). See the updated manual pages
for more details. [issues #3329, #3411]
powervar_cx_usb, tripplite_usb drivers used a built-in limit on
reconnection attempts after which they exited (60 and 10 respectively).
This was revised to follow the new common setting reconnect_max_tries,
which defaults to trying indefinitely now. [#3541]
nutdrv_qx driver with cypress subdriver may be impacted
by a fix which added a cypress_0665_5161_subdriver initialization method for
devices with USB ID 0665:5161 (Belkin, Voltronic, VOLT Polska) which enables
a special quirk to drain stale bytes from USB buffers of the device before our
driver sends queries, and use a longer timeout. If this change breaks your
device, please add cypress_drain_quirk = 0 in your ups.conf and let us
know. [issue #2534, PR #3563]
huawei-ups2000 driver fixed two serious problems that affected all
previous NUT versions. All huawei-ups2000 users are strongly recommended
to upgrade to NUT 2.8.6, all previous versions are considered too unreliable
to use. Due to a Modbus compatibility problem, it was not possible to write
to any registers at all on some UPS models, meaning that changing any
variable or sending any instant command was impossible. Furthermore, due
to a broken instant command handler, some instant commands would always fail
with a reg1 is negative error (even with a compatible UPS), including
bypass.start, shutdown.return, shutdown.reboot, and
shutdown.reboot.graceful. [issue #3593, #3603, PR #3604].