On Sep 11, 2016, at 3:37 PM, Jeff Bowman <[email protected]> wrote:
>
> Using subdriver: APC HID 0.95
>
> ...and then hangs for 45 seconds before returning to a command prompt. No UPS
> hardware information is printed.
It can take about that long to read the descriptors. The non-Windows NUT
drivers will print that message, then return to the command line when they go
into the background (seems similar to your case, if I understand that you ran
the PowerShell process list command after that 45-second wait).
Speaking of which, what version of NUT is this? Given the exact version string,
those without Windows systems can at least look at the source code. I know
there are some differences in the logging, but I don't recall the specifics.
Here's the NUT stack:
UPS <-> Driver (usbhid-ups) <-> Server (upsd) <-> Clients (upsmon, upsc)
I think you have that first link working (assuming usbhid-ups is still
running). If the server is not running, you can try starting it manually with
one or more "-D" flags to see what is going wrong.
On the other hand, if the driver is only running for that 45 second interval,
you can also run the driver manually with "-D". ("upsdrvctl start" is primarily
a shortcut for systems that stash the drivers out of $PATH, and also to start
multiple drivers in sequence.)
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
