packages/net/nut/files/nut-server.init, branch master

nut: fix no permissions to use USB UPS, and more

2026-03-03T18:53:14Z

When a USB UPS is first configured, the permissions on the device under `/dev/bus/usb` have not yet been set to allow the nut user access. This resulted in errors such as: Fri Feb 13 23:39:01 2026 daemon.debug upsd[3504]: [D1] mainloop: UPS [eco550ups] is not currently connected, trying to reconnect Fri Feb 13 23:39:01 2026 daemon.debug upsd[3504]: [D1] mainloop: UPS [eco550ups] is still not connected (FD -1) Fri Feb 13 23:39:03 2026 daemon.debug upsd[3504]: [D1] mainloop: UPS [eco550ups] is not currently connected, trying to reconnect Fri Feb 13 23:39:03 2026 daemon.debug upsd[3504]: [D1] mainloop: UPS [eco550ups] is still not connected (FD -1) or Fri Feb 13 23:38:44 2026 daemon.err usbhid-ups[3083]: No matching HID UPS found Fri Feb 13 23:38:49 2026 daemon.warn procd: failed adding instance cgroup for nut-server: No error information Fri Feb 13 23:38:49 2026 daemon.err usbhid-ups[3115]: libusb1: Could not open any HID devices: insufficient permissions on everything Fri Feb 13 23:38:49 2026 daemon.err usbhid-ups[3115]: No matching HID UPS found Fri Feb 13 23:38:54 2026 daemon.warn procd: failed adding instance cgroup for nut-server: No error information and upsd would enter a procd crashloop. We fix that by looking in `sysfs` (under `/sys/devices`) to find the correct USB device and set its ownership and permissions to allow acces to the user the driver is running under. Copilot complained about a few things * nut-server.init had potential word-splitting issues in various spots. * it also had some commands missing an argument * improved documentation was required to clarify a dependency * an incorrect sed could mangle names as well as remove the intended name Additionally, while fixing those issues the author noticed that the case of multiple UPS devices with the same vendorid:productid were not correctly handled. A check of the serial number, if provided, was added along with a fallback to allowing NUT communications with all UPS devices with a given vendorid:productid, if no serial number was given. Improve efficiency and decrease McCabe complexity of ensure_usb_ups_access, while also fixing Copilot complaints. $@ in case is a problem, and we only handle the first parameter in any event, so change $@ to "$1" Copilot caught a missing 2>&1 and we silence some shellcheck false positives Signed-off-by: Daniel F. Dickinson

nut: comment and simplify server script

2026-03-03T18:53:14Z

Attempt to de-mystify the nut-server initscript by adding comments and factoring out some common code that adds to complexity of the functions of which it is part. Signed-off-by: Daniel F. Dickinson

nut: stop de-configured ups

2026-03-03T18:53:14Z

Ensure that when a ups is removed from the configuration that its driver instance is stopped. Signed-off-by: Daniel F. Dickinson

nut: fix driver, server, and monitor reload/stop

2026-03-03T18:53:14Z

Updated configuration was not being applied after config change. This was due to the means used to do the daemon reloads. Closes #28298 "Drivers not restarted on config change" Enable creating PID files for the server, driver, and monitor daemon processes. This allows to use NUT's built-in facilities for signalling the daemon's. For server, when reloading: 1. Check if upsd is running 1. If not, start it. 2. If it is send reload signal to upsd 2. For each driver: 1. Check if the driver is running 1. If it is, send reload-or-exit signal to driver 2. If driver is not running, start it 3. Attempt to start server (upsd and drivers) if service was stopped. For server, when stopping: 1. Check if upsd is running 1. If it is send stop signal to upsd 2. Ensure it really is stopped 2. For each driver: 1. Check if the driver is running 1. If it is, send stop signal to driver 2. If driver is still running, stop it. 3. If the server process is active (even with not upsd or drivers), stop it. For monitor, send the reload signal on config change, with fallback to stopping and starting the daemon. Change the names of variables and functions to make it more clear what is being acted on, configured, or otherwise touched. Avoid confusing messages in syslog * Avoid attempting to remove a procd server instance that does not exist as doing so results in confusing/scary messages in syslog, such as: Command failed: ubus call service delete { "name": "nut-server", "instance": "upsd" } (Not found) In NUT some models of UPS use shutdown_delay rather than offdelay, and yet others use usd for the same purpose. shutdown_delay and usd were previously not available in the list of available driver options, so add them. Signed-off-by: Daniel F. Dickinson

nut: add linting and fix whitespace and typos

2026-03-03T18:53:14Z

shellcheck is a useful linter if a bit pedantic and overzealous so add overrides to silence false positives Also, fix issues found by the linting. * misspelling meant initscript could skip updating configuration in certain circumstances * minor: assignment of the result of execution as the time of creating local. This has been separated. Fix whitespace and comment typos Fix typo in Config.in option text * This is cosmetic, but user-facing (for users building via SDK or buildroot). Signed-off-by: Daniel F. Dickinson

nut: add cable type nut driver config

2022-05-13T04:53:27Z

at least driver apcsmart-old (maybe more) allow for specifying the type of cable used. My old UPS does will not function when cable type is not specified. This will add support for configuration option 'cable' Signed-off-by: Rob J. Epping

nut: Add the option to compile Nut NetXML drivers with the Nut package.

2021-09-23T20:03:10Z

Also modifies the nut-server init script to include options specific to the netxml driver. Signed-off-by: Seb Belcher

nut: fix _ handling

2020-09-19T23:52:58Z

Taken from https://github.com/openwrt/packages/issues/13359 Signed-off-by: Rosen Penev

nut: fix other/otherflag custom variables in nut-server.init

2020-01-20T03:39:44Z

This allows custom config parameters to be added to the generated config files, enabling the original intended functionality per https://openwrt.org/docs/guide-user/services/ups/software.nut. Example usage from /etc/config/nut_server: config driver 'apc' option driver 'snmp-ups' option snmp_version 'v3' option port '172.16.100.5' list other 'secLevel' list other 'secName' list other 'authPassword' list otherflag 'notransferoids' config other 'other_secLevel' option value 'authNoPriv' config other 'other_secName' option value 'some_username' config other 'other_authPassword' option value 'some_password' config other 'otherflag_notransferoids' option value '1' Signed-off-by: Matt Merhar

nut: initscripts hotplug: Fix many small semantic issues

2019-01-20T17:16:28Z

Small but important tweaks to fix the operation of the nut initscripts and hotplug scripts. All hail shellcheck and proofreading and dogfooding. Signed-off-by: Daniel F. Dickinson