Re: upower forgets UPS when nut-server starts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 3/30/22 9:24 AM, Roger Heflin wrote:
nut-server seems to connect to the device and tie up its port.

It appears upower only accesses the device every so often and queries it.

So then once nut-server is started upower cannot open the device again.

It comes down to you cannot really have 2 separate software stacks managing any single device as it is rare that anyone writes their specific stack to play nice with others. nut-server is quite old and I know it opens and keeps open the port to the ups, mainly because it manages some old upses with very primitive control cables (not strictly serial connections).

There might be a way to configure upower and/or the applet to query nut-server rather than the ups. Though doing a quick look at upowerd the documentation seems sparse.

Just now I found a clue that suggests that NUT is somewhat aware of upower. There's a UDEV rules file named 95-upower-hid.rules that comes from the NUT project:

https://github.com/networkupstools/nut/blob/master/scripts/upower/95-upower-hid.rules

A file of this name is installed on my Fedora 34 systems, but it is packaged with upower:

$ rpm -qf /usr/lib/udev/rules.d/95-upower-hid.rules
upower-0.99.13-1.fc34.x86_64

The file begins with this text:

# Uninterruptible Power Supplies with USB HID interfaces
#
# This file was automatically generated by NUT:
# https://github.com/networkupstools/nut/

Also, there's an open NUT issue that relates to upower but it's not been updated since 2018:

https://github.com/networkupstools/nut/issues/526

The reason I'm using NUT, as opposed to apcupsd (which does play nice with upower), is that I have a couple of Synology NASes that have built-in NUT support. These NASes are connected to the same UPS as one of my Linux systems so I have the Linux system acting as NUT server with the NASes acting as NUT clients.

Dave



_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux