Hello,

I've experienced the upstream's high CPU usage bug[1] for the upssched
process when using upshid-ups and dummy-ups configuration in
upssched.conf. Essentially the very same directives that are presented
in the upstream's bug. As per Github's repository the issue has been
fixed in a patch that is already available and merged upstream[2], back
in 2023.

I've looked at the Debian patch tracker and didn't found anything
related to this. I understand version 2.8.1 includes such fix, but since
2.8.0 is included in the stable version and the bug compromises system's
resources, perhaps we need to include the patch.

Thank you.


1- https://github.com/networkupstools/nut/issues/2009
2- https://github.com/networkupstools/nut/pull/2155

On Sun, 16 Feb 2025 23:39:56 -0500 Rudy Godoy <hola@rudygodoy.com> wrote:

 > Hello,

Hello Rudy,

 > I've experienced the upstream's high CPU usage bug[1] for the upssched
 > process when using upshid-ups and dummy-ups configuration in
 > upssched.conf. Essentially the very same directives that are presented
 > in the upstream's bug. As per Github's repository the issue has been
 > fixed in a patch that is already available and merged upstream[2], back
 > in 2023.
 >
 > I've looked at the Debian patch tracker and didn't found anything
 > related to this. I understand version 2.8.1 includes such fix, but since
 > 2.8.0 is included in the stable version and the bug compromises system's
 > resources, perhaps we need to include the patch.

Sorry for the really late answer.

I see that you marked this bug as found in 2.8.1, is it really the case?
Or is it fixed in that version?

Kind regards,

Laurent Bigonville