[Nut-upsuser] usbhid-ups flooding system log

[Raymond Burkholder]

On 2026-07-23 18:49, Robert Nichols via Nut-upsuser wrote:
> Thanks for the response, but this is a different situation. In my 
> case, the device actually _is_ disconnected (I disconnected the USB 
> cable and shut down the UPS prior to replacing the batteries). This is 
> not the only UPS, and it's not even the primary one for this host, so 
> I do not want to stop nut.target. Restarting nut.target is not going 
> to help unless I first edit the ups.conf, upsmon.conf, and hosts.conf 
> files to remove references to the now disconnected unit, though now 
> that I think of it, perhaps if the device is missing right from the 
> start, then the package won't keep trying forever to look for it. I'll 
> give that a try some time. 

You could get really funky with the scripts.  The udev is UPS specific 
(each UPS should have a unique dev/identifier) and thus a specific 
rule.  If a specific UPS disappears, swap out/in config files (or run 
sed on files) and restart the nut.target.

You can be dynamic as UPS instances come and go.

Raymond
https://blog.raymond.burkholder.net/