Hi all,
Well, I must be missing something so obvious, that it isn't even in
the documentation: How to stop all instances of a driver.
I tried this on my system, since I use the usbhid-ups:
n...@grisen:~$ ps ax | grep usbhid
238 ? S 0:00 [usbhid_resumer]
1035 ? Ss 37:14 /lib/nut/usbhid-ups -a PingvinUPS
24223 pts/0 S+ 0:00 grep usbhid
I would not dare to use "kill" on neither the usbhid_resumer nor the
usbhid-ups with the system running in a remote location.
/lib/nut/usbhid-ups -h gives no clue about how to shut down, the "-k"
option probably would shut down the UPS, not the driver.
So I searched the mail archives using keywords:
"error sending control message"
"libusb_get_report"
If some useful answer came up, I failed to find it.
Searching with google:
libusb_get_report site:www.networkupstools.org
and
debug site:www.networkupstools.org
Nothing here, either.
Can someone tell me how? Please be gentle, I feel like this should be
a simple task...
Best regards,
Niels Kristian Jensen
Quoting Arjen de Korte <[email protected]>:
Citeren Niels Kristian Jensen <[email protected]>:
(many more resource errors follow)
The last lines are telling you what is going on:
4.547868 libusb_get_report: error sending control message: Device or
resource busy
4.547886 Can't retrieve Report 06: Device or resource busy
4.547900 Got disconnected by another driver: Device or resource busy
Well, I probably need to shut down NUT somehow to release the resource?
Yes. You can only claim a device once, so in order to get meaningful
output, you must stop all instances of usbhid-ups before starting it in
debug mode.
Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
