On 4/7/23 16:17, Orion Poplawski wrote:
On 4/6/23 21:27, Robert Nichols wrote:
...
The user needs to enable nut-driver-enumerator.service if there is any UPS
hardware monitored by this system (i.e., not needed if this is a "secondary"
system and some other "primary" system is actually monitoring the UPS).
Why should the user have to explicitly enable nut-driver-enumerator.service?
It does seem necessary for some reason to enable it to have it start with
nut.target below. But I don't understand why. It has PartOf=nut.target:
[Unit]
# This unit starts early in system lifecycle to set up nut-driver instances.
# End-user may also restart this unit after editing ups.conf to automatically
# un-register or add new instances as appropriate.
Description=Network UPS Tools - enumeration of configure-file devices into
systemd unit instances
After=local-fs.target
Before=nut-driver.target
PartOf=nut.target
just like nut-server.service:
But nut.driver.target is an empty target that contains no "wants". If you
enable nut-driver-enumerator.service, that generates a link in
/etc/systemd/system/nut.target.wants, so the enumerator gets started when
nut.target starts. Unless the user explicitly enables the enumerator
service, nothing starts it.
I had some discussion of this with the developer on
<https://github.com/networkupstools/nut/issues/1851#issuecomment-1436621461>.
The developer seems to feel it's just a documentation issue. The docs
currently imply that the enumerator starts automatically.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
