BS> My second thought was to put it into LM-SENSORS-MIB. That MIB, though
BS> appears to be geared specifically to the lm-sensors package for linux.
RS>That is exactly where you should be going. The MIB is not specific to
RS>lm-sensors, other than containing the name. If you look at the mib, it's pretty
RS>generic. It has tables for temperatures, fans, voltage and misc.
OK, then that's where it'll go.
BS> Next problem is that the methodology used to derive the CPU temperature on
BS> one specific piece of Sun hardware is different on another piece. The
BS> net-snmp code could get really, really messy.
RS>Try and find a way to make it nice and generic at the mib level. Maybe a table
drive approach.
It looks like I can work within LM-SENSORS-MIB
BS> A subsequent problem is that my code may be in violation of Sun's licensing
BS> agreement. However, it is based upon .h files found within their published
BS> operating system, so presumably the code could be published with Copyright
BS> disclaimers similar to those already inserted by Sun's contributing
BS> engineers (Hi, guys!!).
RS>Are you using documented API calls? As long as you don't have access to
RS>proprietary information, are not under a non-disclosure agreement and wrote the
RS>code yourself (not copied from copyrighted code), you are probably ok.
I'm using *.h files as includes. They are part of the operating system so I have to assume they're open season. I'm also using the notoriously un/under-documented kstat interface, but we're already doing that in half-a-dozen places. Sun slapped a copyright notice on it, so we'll do the same here.
BS> This may also apply to using my code to populate Sun's MIB.
RS>If the MIB is publicly available, they can't stop your from implementing it in
an agent.
It looks like LM-SENSORS-MIB will suit my purposes so this is moot.
BS> So here's how I see it working so far. I create a binary that works on
BS> such-and-such hardware with the appropriate disclaimers (use at your own
BS> risk, don't sue me I don't have any money) with a published API.
RS>I hope by binary you mean library.
What I actually meant was both. For my own purposes I need a stand-alone app. For our purposes we need a library. My stand-alone could use our library. As we discussed on IRC.
BS> 2. The Solaris net-snmp community is reliant upon me (as coder of the
BS> helper app) not to get hit by a bus/jitney/taxi/rickshaw/hovercraft.
RS>Not if you make it open source. Start your own project on sourceforge.
Sounds like an idea.
BS> 3. I've only got a limited range of hardware at my disposal. Others may
BS> have code to contribute for other platforms but can't because I'm hogging
BS> the source to the helper app.
RS>See #2. Accept patches.
ibid.
This communication is intended for the use of the recipient to which it is addressed, and may contain confidential, personal and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communication received in error, or subsequent reply, should be deleted or destroyed.
