>>so how do we make it happen? do we just wait for a developer to respond? I >>for one will definitely use it.
If you can submit a patch, this would probably help ;-) Otherwise, you'll have to wait for it to happen. Francois Isabelle -----Message d'origine----- De : Mark Seger [mailto:[EMAIL PROTECTED] Envoyé : 26 novembre 2008 10:11 À : Isabelle, Francois Cc : Carol Hebert; ipmitool-devel@lists.sourceforge.net Objet : Re: [Ipmitool-devel] Optimizing the use of ipmitool >>> The idea here is to be able to correlate power >>> > consumption against cpu load and individual processes which is something > a lot of people are interested in. > > This is interesting indeed. > why don't you check out collectl and see for yourself. For example on my system I can see: [EMAIL PROTECTED] ~]# collectl -i1::1 -scE waiting for 1 second sample... ### RECORD 1 >>> hadesn1 <<< (1227711805.003) (Wed Nov 26 10:03:25 2008) ### # CPU SUMMARY (INTR, CTXSW & PROC /sec) # USER NICE SYS WAIT IRQ SOFT STEAL IDLE INTR CTXSW PROC RUNQ RUN AVG1 AVG5 AVG15 0 0 0 0 0 0 0 99 1034 2056 2 168 0 0.00 0.00 0.00 # ENVIRONMENTAL STATISTICS # VFan Temp1 Temp2 Temp3 Temp4 Temp5 Temp6 Temp7 Temp8 Temp9 37.240 47 34 30 30 32 30 30 57 24 the first '1' in -i1::1 command says to collectl 'standard' data once a second and the second one means to collect what I'm calling environmental data once a second too - much to frequently that necessary (I think) but it's a nice way to show both. My plan would be to add watts as another column. The neat thing here is you can also log the data to a file and even record it in what I call 'plot format', making it real easy to hand off to gnuplot! check it out... >>> If you can't specify multiple sensors with a single command is there any >>> thought/interest is providing that as an enhancement? >>> > > I'm guessing that if you suggest a command line format like: > > ipmitool sdr types [command separated type list] > > so you could run: > > ipmitool -S file sdr types temp,current,fan > > It could be useful to others as well, you get less processes spawned and in > case of an IOL connection, you don't needlessly authenticate over and over > again. > that's exactly what I was thinking though I make this the behavior of the 'type' option and not include a second form. in fact there may even be other commands where this is useful but I'll leave that for others to decide. I'd also like to make sure it works with -c since I like this output format for easy parsing. so how do we make it happen? do we just wait for a developer to respond? I for one will definitely use it. -mark > I'd vote for this feature as well ! > > Francois Isabelle > > -----Message d'origine----- > De : Mark Seger [mailto:[EMAIL PROTECTED] > Envoyé : 26 novembre 2008 09:19 > À : Isabelle, Francois > Cc : Carol Hebert; ipmitool-devel@lists.sourceforge.net > Objet : Re: [Ipmitool-devel] Optimizing the use of ipmitool > > > > Isabelle, Francois wrote: > >> >> >>> I did discover the "ipmitool sdr get" command which the help says takes >>> an id as a target but when I tried it, it didn't work! >>> >>> >> And make sure you run: >> ' ipmitool sdr dump <file>' >> and >> 'ipmitool sdr get "Power Meter" -S <file>' >> >> to skip over the lengthy discovery process (unless the sensor population is >> dynamic). >> >> > yes, I've been doing that. by my main problem still remains. I want to > get 3 sensors: fans, temps and power and want to do it with a single > ipmitool command if possible to make things more efficient and simply > doing "ipmitool -S file sdr" with no args is a lot slower on some > systems than individually doing: > > ipmitool -S file sdr type temp > ipmitool -S file sdr type fan > ipmitool -S file sdr type current # gets me the power. > > I don't recall it I mentioned this or not, but I'm the author of > collectl, see - http://collectl.sourceforge.net/, which in many ways is > similar to a performance data collection tool like sar, but add a lot > more data types and provides a lot more ways to view the data. In any > event, I've including ipmi sensor monitoring via ipmitool for fans and > temperature sensors which is very cool, and now I want to add power > monitoring but want to be as efficient as I can since collectl runs > continuously. The idea here is to be able to correlate power > consumption against cpu load and individual processes which is something > a lot of people are interested in. Collectl is very efficient, > typically using less than 0.1% of the cpu when sampling at a frequency > of 10 seconds. By default I'm setting the frequency of ipmitool > monitoring to once every couple of minutes since it does have more > overhead than reading data out of proc. My fear is having to invoke it > multiple times/sample is too heavyweight and so I'm looking for > alternatives. If you can't specify multiple sensors with a single > command is there any thought/interest is providing that as an > enhancement? I think it would be a very useful (and probably not that > hard) thing to do... > > -mark > > >> Francois Isabelle >> >> -----Message d'origine----- >> De : Carol Hebert [mailto:[EMAIL PROTECTED] >> Envoyé : 25 novembre 2008 15:45 >> À : Mark Seger >> Cc : ipmitool-devel@lists.sourceforge.net >> Objet : Re: [Ipmitool-devel] Optimizing the use of ipmitool >> >> Quoting Mark Seger <[EMAIL PROTECTED]>: >> >> >> >>> I did discover the "ipmitool sdr get" command which the help says takes >>> an id as a target but when I tried it, it didn't work! First I did this >>> to get a list of IDs: >>> >>> [EMAIL PROTECTED] ~]# ipmitool sdr elist >>> UID Light | 01h | ok | 23.1 | 0 unspecified >>> Int. Health LED | 02h | ok | 23.2 | 0 unspecified >>> VRM 1 | 03h | lcr | 9.1 | 0 unspecified >>> VRM 2 | 04h | lcr | 9.2 | 0 unspecified >>> Temp 1 | 05h | ok | 7.1 | 47 degrees C >>> Temp 2 | 06h | ok | 3.1 | 34 degrees C >>> Temp 3 | 07h | ok | 3.2 | 30 degrees C >>> Temp 4 | 08h | ok | 3.3 | 30 degrees C >>> Temp 5 | 09h | ok | 3.4 | 32 degrees C >>> Temp 6 | 0Ah | ok | 3.5 | 30 degrees C >>> Temp 7 | 0Bh | ok | 3.6 | 30 degrees C >>> Temp 8 | 0Ch | ok | 8.1 | 57 degrees C >>> Temp 9 | 0Dh | ok | 39.1 | 24 degrees C >>> Virtual Fan | 0Eh | lnc | 7.2 | 37.24 unspecifi >>> Enclosure Status | 0Fh | ok | 23.3 | 0 unspecified >>> Power Meter | 10h | lcr | 7.3 | 204 Watts >>> >>> but when I did this, it didn't: >>> [EMAIL PROTECTED] ~]# ipmitool sdr get 10h >>> Unable to find sensor id '10h' >>> >>> >>> >> Try ' ipmitool sdr get "Power Meter" ' >> >> Hope this helps, >> >> Carol >> >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge >> Build the coolest Linux based applications with Moblin SDK & win great prizes >> Grand prize is a trip for two to an Open Source event anywhere in the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> Ipmitool-devel mailing list >> Ipmitool-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/ipmitool-devel >> >> > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
