All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] sensord with rrd
Date: Wed, 14 Jan 2009 20:39:28 +0000	[thread overview]
Message-ID: <20090114213928.494ed777@hyperion.delvare> (raw)
In-Reply-To: <gkimcg$46k$1@ger.gmane.org>

Hi Mark,

On Wed, 14 Jan 2009 12:26:45 -0800, Mark E. Hansen wrote:
> FYI: I just installed CentOS 5.2 on a machine here and had to go back
> to lm-sensors 2.10.6, as the 3.0.3 version would not produce alarms
> in the sensors output, even when readings were beyond their configured
> limits. After moving back to 2.10.6, the alarms worked as expected.
> My motherboard and sensors chip is different than the OP's, so this
> may not apply to him.

Nice thread hi-jacking ;)

> Note: I did post a question to this list about this issue, but have
> yet to receive any responses.

That was during vacation, when not that many developers take the time
to read the mailing list.

Alarms are the last piece that has been ported to the standard sysfs
interface (which lm-sensors 3 builds on top of.) See
http://www.lm-sensors.org/ticket/2261
for a list of drivers that have been fixed in recent kernels. So
basically for proper alarm support with lm-sensors 3.x you need a
recent enough kernel.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2009-01-14 20:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13 18:26 [lm-sensors] sensord with rrd Mark Nienberg
2009-01-14 10:32 ` Jean Delvare
2009-01-14 17:57 ` Mark Nienberg
2009-01-14 18:44 ` Jean Delvare
2009-01-14 19:01 ` Mark Nienberg
2009-01-14 20:03 ` Jean Delvare
2009-01-14 20:26 ` Mark E. Hansen
2009-01-14 20:39 ` Jean Delvare [this message]
2009-01-14 20:54 ` Mark Nienberg
2009-01-14 21:08 ` Mark E. Hansen
2009-01-14 21:58 ` Jean Delvare
2009-01-14 22:12 ` Mark E. Hansen

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=20090114213928.494ed777@hyperion.delvare \
    --to=khali@linux-fr.org \
    --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.