Charles,
Once again thanks for your help and patience with me. I did more
investigation of things, made some more group changes and even edited my
hosts file since localhost was in there twice (once on 127.0.0.1 and
once on some ip6 entry). Somewhere in all of that, I seem to have things
running and I can see both the blazer_usb driver and upsmon in the
results of a ps command. I can also issue a upsc belkinusb command and
see the ups properties.
This is a single computer on this ups. And I simply want to have a
script called when the ups reports going on battery. do I need the
nut-client going at all?
Cheers
On 1/23/2021 3:01 PM, Charles Lepple wrote:
On Jan 23, 2021, at 1:07 PM, David White via Nut-upsuser
<[email protected]> wrote:
I did the chmod myself thinking that there might be some odd access/permission
problem and will change it back since that hasn't changed diddly.
ls -l /dev/bus/usb/001/003 shows:
crw-rw----. 1 root aid_usb 189, 2 Jan 23 00:06 /dev/bus/usb/001/003
Is the NUT system user in the aid_usb group? That is the recommended way to fix
this, though you could try to alter whatever is setting that group on the /dev
node, or do something else with permissions.
If your version of NUT has nutdrv_qx, that's about the only other driver I
would expect to work with that hardware.
_______________________________________________
Nut-upsuser mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
