If the distro packaging follows vanilla NUT reference units, disabling `nut.target` alone should suffice.
Otherwise, NDE-made units for drivers are likely tripped by a same-named timer unit that re-runs NDE and spawns missing drivers (though disable/mask also for each `[email protected]` should preclude them starting by timer or other ways). Hope this helps, Jim Klimov On Thu, Nov 28, 2024, 20:12 <[email protected]> wrote: > I would like to keep NUT installed but disable it completely at times. > I tried both 'disabling' and 'masking' all the following 'systemctl > services > nut-server > nut-monitor > nut-client > ups-monitor > nut-driver-enumerator > as follows: > systemctl disable nut-server nut-monitor nut-client ups-monitor > nut-driver-enumerator > systemctl mask nut-server nut-monitor nut-client ups-monitor > nut-driver-enumerator > > But I still have 2 '/sbin/upsdrvctl' processes that are respawned > periodically: > Specifically: > root 123446 0.1 0.2 2320 1280 ? Ss 11:27 0:00 > /bin/sh -c NUTDEV="`/usr/libexec/nut-driver-enumerator.sh > --get-device-for-service APC_RS900`" && [ -n "$NUTDEV" ] || { echo "FATAL: > Could not find a NUT device section for service unit APC_RS900" >&2 ; exit > 1 ; } ; /sbin/upsdrvctl start "$NUTDEV" > root 123473 0.0 0.3 2220 1408 ? S 11:27 0:00 > /sbin/upsdrvctl start APC_RS900 > > These processes respawn every few minutes and clutter my syslog with error > messages. > > So, what do I need to do to fully disable NUT? > And what are the minimum services I need to disable to make this take > effect... > > I am running Bookworm/Debian 12 on a RPI5. > > _______________________________________________ > Nut-upsuser mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
