[nut-Patches][313846] nut apcupsd client driver

[nut-patches at alioth.debian.org]

nut-Patches item #313846, was changed at 25/10/2012 21:10 by Arnaud Quette
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=411544&aid=313846&group_id=30602

Status: Pending
Priority: 4
Submitted By: Andreas Steinmetz (anstein-guest)
Assigned to: Charles Lepple (clepple-guest)
Summary: nut apcupsd client driver 
Category: New driver
Group: None
Resolution: Accepted


Initial Comment:
I do have to access an APC UPS via PowerChute Client (pcnet) mode, which is supported by apcupsd and all of my regular systems are running apcupsd.

Furthermore I'm running QNAP NAS systems that require me to serve UPS data via nut. Thus I do need an apcupsd client driver for nut, which I do attach.

The attached patch is against nut-2.6.3 which is the current Gentoo version of nut. This, however, shouldn't be a problem.

----------------------------------------------------------------------

>Comment By: Arnaud Quette (aquette)
Date: 25/10/2012 21:10

Message:
the original post from Charles mentioned the 2 following conditions for a  "trunk readiness":
> 1) add some common IPv6 TCP connection code, and use that in the driver
> 2) write up some documentation, such as a transition/interoperability guide and a variable mapping table

In light of this, there is a bit more work needed...

----------------------------------------------------------------------

Comment By: Arnaud Quette (aquette)
Date: 25/10/2012 20:46

Message:
As discussed privately with Charles, the last missing bit is to add a reference in the "generic device drivers" section of the user documentation:
http://www.networkupstools.org/docs/user-manual.chunked/ar01s02.html#_generic_device_drivers

a patch is attached (apcupsd-ups-doc.diff)

- side note: I definitely have to make some generic functions and structs for data mapping and value lookup

----------------------------------------------------------------------

Comment By: Charles Lepple (clepple-guest)
Date: 01/10/2012 14:08

Message:
Arnaud: OS X doesn't have a "detach driver" request like Linux, and apcupsd has all of the "driverless KEXT" support to make it work out of the box. We're getting there, though.

Andreas: Not sure if you're monitoring "ups.load" in NUT, but there was an extra multiplier on that variable. I also added a few more variables to the Git branch: https://github.com/clepple/nut/commits/git-apcupsd/

----------------------------------------------------------------------

Comment By: Arnaud Quette (aquette)
Date: 01/10/2012 10:35

Message:
Interesting!
And both on the driver itself, and Charles' comment:
"...apcupsd still does a better job than NUT for accessing APC hardware on OS X."

@Charles: what is missing from nut to be on par with apcupsd?
Is it just related to OS X or is it in general?

----------------------------------------------------------------------

Comment By: Charles Lepple (clepple-guest)
Date: 28/09/2012 04:23

Message:
Thanks for your patch! I would like to try this on one of my systems, since apcupsd still does a better job than NUT for accessing APC hardware on OS X.

I applied it to my Git mirror of the SVN trunk, and there were no conflicts (not surprisingly, given how recent 2.6.3 is). Here are a few minor additions to the comments and documentation:

https://github.com/clepple/nut/commit/b37b7cba2abc3c5d4d1747a442f3ca85535647c2

Since the core of NUT is GPLv2, and drivers link against that, I added that license boilerplate to the beginning of the source. Also, I'll poke around and see if we have some canned IPv6-compatible TCP code to add - otherwise, some of that can be added to common/

----------------------------------------------------------------------

You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=411544&aid=313846&group_id=30602