check_lm_sensors and the correct sensor names for checking cpu temperatures

[Rahul Nabar]

On Tue, Feb 10, 2009 at 3:03 PM, Rahul Nabar <rpnabar at gmail.com> wrote:

>
>
> On Tue, Feb 10, 2009 at 2:57 PM, Matteo Corti <matteo.corti at gmail.com>wrote:
>
>> Dear Rahul,
>> Please post the output of "/usr/local/nagios/libexec/check_lm_sensors
>> --list"
>> Maybe, the --list option should tell us what "check_lm_sensors" sees but
>> since it parses the output of sensors it should work.
>>
>>
> Thanks again Matteo!
>
> usr/local/nagios/libexec/check_lm_sensors --list
> LM_SENSORS OK - |
>
> That's the only output I get.


Just a thought:

Could it have something to do with my $LANG variable? It was set to
en_US.UTF-8 earlier and then in the output of sensors the "centigrade" sign
appeared messed up.

Once I set it to export LANG=en_EN it appears correctly. Could this be
screwing up the regexes inside  check_lm_sensors?

If so, what's the workaround? Maybe I'm totally off the mark and this is
just a red herring.

-- 
Rahul
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090210/324499b6/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null