Ok, that did work on a T2000 (strange, I thought I'd tried that one already) but doesn't on a V490.
I take it if they don't show up in prtdiag -v they're just plain not available? They're not showing up on the ALOM either. -----Original Message----- From: Peter Tribble [mailto:[email protected]] Sent: Tuesday, August 18, 2009 2:37 PM To: Bruce Shaw Cc: observability-discuss at opensolaris.org Subject: Re: [observability-discuss] Am I missing something, or is there no programmatic interface to IPMI On Tue, Aug 18, 2009 at 8:10 PM, Bruce Shaw<Bruce.Shaw at gov.ab.ca> wrote: >>prtpicl -c rpm-sensor -v > > That worked on a T2000. ?I wish the names would stop changing on these > things. (how's that for passive voice) They do appear to be rather random. > However, I still haven't found the power supply voltages for either. Again on a T5140: prtpicl -c voltage-sensor -v It would be nice to have programmatic APIs - or language bindings - to this so you can get at the data from perl/python/java. I did write a Java interface once. The idea was to display a graphical tree and allow the user to drill down, which would work as the picl data is essentially hierarchical. Unfortunately the JNI code simply crashes, and I've never been able to work out why. Another patch I had was a -n flag to prtpicl, to just display a given node by name, so you have to do less post-processing of the output. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
