All of lore.kernel.org
 help / color / mirror / Atom feed
From: paul@astropaul.com (Paul Reilly)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] IPMI sysfs support for 2.6.16.x
Date: Tue, 20 Feb 2007 13:07:17 +0000	[thread overview]
Message-ID: <1171976837.45daf28524626@mail.third-rock.net> (raw)
In-Reply-To: <1171733778.45d73d12edf0a@mail.third-rock.net>


Hi Philip,

Thanks for the info, and advice on taking the IPMI approach directly
rather than using lm-sensors. I had not looked at that, and perhaps
it is the best way to go. I'd like to be able to integrate the sensor
data in to Cacti to graph temperatures, fan speeds etc over time. So
if I can do that with  IPMI tool I will use that.

IPMItool certainly looks very good from what I have seen,

Best Regards,
Paul

> Unless there is some specific reason that you want lm_sensors, you might
> find that accessing the temperature readings directly with IPMI methods
> is much easier.  Your kernel likely already has the IPMI drivers and you
> may already have the ipmitool command which gives you access to all the
> BMC features without needing sysfs support.
>
> Penguin Computing has done extensive testing of ipmitool to access the
> BMC both locally and remotely via IPMI over LAN.
>
> Look at the output of 'ipmitool sdr elist' and 'ipmitool sensors'
>
> In addition, with ipmitool you have access to the historical event logs
> (ipmitool sel elist), server control ("ipmitool chassis power status"
> and related "soft" for clean ACPI shutdown, "on", and "reset"), and
> console access (ipmitool sol)
>
> Give Penguin Tech Support a call if you need help getting IPMI working
> on your system.
>
> Thanks,
> Phil Pokorny
> Director of Field Engineering
> Penguin Computing
>


-- 


      parent reply	other threads:[~2007-02-20 13:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-17 17:36 [lm-sensors] IPMI sysfs support for 2.6.16.x Paul Reilly
2007-02-17 23:22 ` Corey Minyard
2007-02-18  0:16 ` Paul Reilly
2007-02-19  8:10 ` Philip Pokorny
2007-02-19 13:40 ` Corey Minyard
2007-02-20 13:07 ` Paul Reilly [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1171976837.45daf28524626@mail.third-rock.net \
    --to=paul@astropaul.com \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.