On Dec 17, 2013, at 12:45 PM, Bruce Bowler wrote: > upsdrvctl stop and start don't complain... > > ------------ > C:\Program Files (x86)\NUT\bin>upsdrvctl stop > Network UPS Tools - UPS driver controller 2.6.5-3723:3731M > > C:\Program Files (x86)\NUT\bin>upsdrvctl start > Network UPS Tools - UPS driver controller 2.6.5-3723:3731M > > C:\Program Files (x86)\NUT\bin>Network UPS Tools - BCMXCP UPS driver > 0.26 (2.6.5 -3723:3731M) > USB communication subdriver 0.21 > -------------
I'm not sure how this works on the Windows port, but you also need upsd running. This diagram shows how the pieces go together: http://www.networkupstools.org/docs/developer-guide.chunked/ar01s02.html#_the_layering > But many other commands complain... > > ------------- > C:\Program Files (x86)\NUT\bin>upsc nutdev1 > Error: Connection failure: Unknown error > ------------- upsdrvctl seems to have successfully started the bcmxcp_usb driver, but for upsc to get data from the driver, it needs to go through upsd. If you have a TCP port listening on 3493, then upsd is running. > For what it's worth, the 'system' is a host with several 'vmware > player' VMs running on it. The eventual goal would be to have the host > running as a nut server and have each of the VMs running a nut client > so they can shut themselves down gracefully in the event of a longer > power outage. Makes sense. Depending on how long a shutdown/startup cycle takes, it could be useful to suspend the VMs. -- Charles Lepple clepple@gmail _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser