search for: sbhid

> Is it possible that there is another copy of the driver running in the background? There is apparently an issue where we only >write a PID file when the driver goes into the background, and "-D" prevents that. I don't see another usbhid-ups running ... unless its "hidden".... I would have to install the unhide package then.... /var/run/devd.pid /var/run/syslog.pid /var/run/mountd.pid /var/run/istgt.pid /var/run/upslog.pid /var/run/upsmon.pid /var/run/powerd.pid /var/run/samba4/nmbd.pid /var/run/samba4/smbd.pid /var/ru...

...nz98 at yahoo.com> wrote: > >> Is it possible that there is another copy of the driver running in the background? There is apparently an issue where we only write a PID file when the driver goes into the background, and "-D" prevents that. > > I don't see another usbhid-ups running ... unless its "hidden".... I would have to install the unhide package then.... > What I mean is that you can't have more than one usbhid-ups process talking to the same UPS at one time - regardless of whether they write a PID file. In the case of running with "...

...ttery.date: 2001/09/25 battery.mfr.date: 2015/05/10 battery.runtime: 14548 battery.runtime.low: 120 battery.type: PbAc battery.voltage: 27.3 battery.voltage.nominal: 24.0 device.mfr: American Power Conversion device.model: Back-UPS XS 1400U device.serial: 3B1519X22971 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: APC HID 0.96 driver.version.internal: 0.41 input.sensitivity: medium input.transfer.high: 280 input.transfer.low: 155 input.tran...

...nz98 at yahoo.com> wrote: > >> Is it possible that there is another copy of the driver running in the background? There is apparently an issue where we only write a PID file when the driver goes into the background, and "-D" prevents that. > > I don't see another usbhid-ups running ... unless its "hidden".... I would have to install the unhide package then.... > What I mean is that you can't have more than one usbhid-ups process talking to the same UPS at one time - regardless of whether they write a PID file. In the case of running with "...

...oice usb 1-3.1: can't set config #1, error -71 and lsusb gives: Bus 001 Device 016: ID 0001:0000 Fry's Electronics The idVendor and idProduct are horrid, alas. I've tried the other usb-type drivers too with debug levels set high (bcmxcp_usb, blazer_usb, richcomm_usb, tripplite_usb and sbhid-ups) and all say "...Device does not match - skipping...." many times finishing with: "No supported UPS detected" I'm at the end of my knowledge here and I can't find anything about this UPS on the 'net - including this list. I'd very much appreciate a pointer...