Files
configpolicy/roles
Dustin C. Hatch 54727e148f r/nut{,-monitor}: Enable nut.target
Recent versions of NUT have a *nut.target* unit that collects all of the
NUT-related services.  Enabling any of the services individually does
effectively nothing, as it only adds the service as a `Wants` dependency
for *nut.target*, and that unit already has dependencies for all of
them. Thus, in order for the service to start at boot, *nut.target* has
to be enabled instead.

In situations where only *nut-monitor* should be enabled, enabling
*nut.target* is inappropriate, since that enables *nut-driver* and
*nut-server* as well. It's not clear why upstream made this change (it
was part of a [HUGE pull request][0]), but restoring the desired
behavior is easy enough by clearing the dependencies from *nut.target*.
Services that we want to start automatically can still be enabled
individually, and will start as long as *nut.target* is enabled.

[0]: https://github.com/networkupstools/nut/pull/330
2024-01-22 09:03:15 -06:00
..
2018-08-08 21:38:56 -05:00
2020-03-09 20:29:52 -05:00
2018-07-23 17:35:10 -05:00
2023-11-13 17:45:21 -06:00
2018-04-08 10:11:43 -05:00
2024-01-22 09:03:15 -06:00
2023-10-24 17:27:21 -05:00
2022-08-15 17:12:35 -05:00
2023-10-28 16:07:39 -05:00
2018-06-06 21:44:28 -05:00
2023-10-21 22:16:28 -05:00
2022-08-15 17:06:20 -05:00
2024-01-21 16:12:29 -06:00
2023-12-17 20:16:51 -06:00