On Sun, Feb 14, 2010 at 9:58 AM, Charles Lepple wrote:
> What does "ps auxww | grep hid" return?
root 372 0.0 0.0 0 0 ?S< 10:50 0:00
[usbhid_resumer]
nut 2485 0.0 0.0 14636 836 ?Ss 10:51 0:00
/lib/nut/usbhid-ups -a apc
_
What does "ps auxww | grep hid" return?
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
> Either multiple instances of usbhid-ups running (are you attempting to
> monitor multiple UPS devices at the same time?) Usually the usbhid-ups
> driver will be started before upsmon and on most systems will have a
> lower PID (not a higher one). Could it be that you attempt to start
> the driver
Citeren Robert McDonald :
And then I sometimes get message like this relating to the driver:
Feb 13 13:59:18 fin8344 upsmon[15163]: Communications with UPS
a...@localhost lost
Feb 13 13:59:18 fin8344 usbhid-ups[15176]: Got disconnected by another
driver: Device or resource busy
Feb 13 13:59:18
I have an APC Back-UPS CS 500 which connects via USB. I am running NUT
2.4.1 under Karmic amd64. The entry in ups.conf is
[apc]
driver = usbhid-ups
port = auto
desc = "APC Back-UPS CS 500"
I left upsd.conf at the default values, nut.conf is "mode standalone",
and in upsmon.conf, the monitor line
5 matches
Mail list logo