Shulou(Shulou.com)06/01 Report--

This article introduces the relevant knowledge of "how to use the software lm_sensors to monitor Linux system and CPU temperature". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

Lm_sensors software can help us to monitor the motherboard, CPU working voltage, fan speed, temperature and other data. These data can usually be seen in the BIOS of the motherboard. When we can monitor the temperature change of the CPU through lm_sensors at any time while the machine is running, we can prevent the protection from burning out because the CPU is overheated.

1. Install lm_sensors

Now basically every Linux already has a lm_sensors package, we can mainly install it. Or we can compile it ourselves through the source file.

1) under FC,RH, CENTOS, use rpm:

[root@securitycn] # rpm-ivh lm_sensors-2.10.0-3.1.i386.rpm

3) compile source file installation

We can download the source file here

The problem we should pay attention to here is to install the libsysfs library, which is the Sysfsutils,Sysfsutils-devel software.

Tar xzvf lm-sensors-xxx.tar.gz

Make user

Make user_install testing

Let's use some simple commands to use lm_sensors to get CPU data. We are going to use the identity of root:

Sensors-detect, and then it will automatically search for the chipset and the corresponding driver on the motherboard. We can answer all YES.

[root@securitycn ~] # sensors-detect

# sensors-detect revision 1.413 (20:28:00 on 2006-01-19)

This program will help you determine which I2C/SMBus modules you need to

Load to use lm_sensors most effectively. You need to have i2c and

Lm_sensors installed before running this program.

Also, you need to be `root', or at least have access to the / dev/i2c-*

Files, for most things.

If you have patched your kernel and have some drivers built in, you can

Safely answer NO if asked to load some modules. In this case, things may

Seem a bit confusing, but they will still work.

It is generally safe and recommended to accept the default answers to all

Questions, unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.

You do not need any special privileges for this.

Do you want to probe now? (YES/no):

All default YES is fine.

Then we start lm_sensors:

/ etc/init.d/lm_sensors start

Starting lm_sensors: [OK]

We can use lsmod to determine whether the driver we need has been loaded.

Lsmod | grep i2C

I2c_isa 9153 2 w83627hf,w83781d

I2c_i801 11341 0

I2c_dev 12613 0

I2c_ec 9025 1 sbs

I2c_core 23745 6 w83627hf,w83781d,i2c_isa,i2c_i801,i2c_dev,i2c_ec

Then we can use the command of sensors:

[root@securitycn ~] # sensors

W83627hf-isa-0290

Adapter: ISA adapter consists of 2 pages.

VCore 1: + 3.33V (min = + 0.00V, max = + 0.00V) ALARM

VCore 2: + 3.36V (min = + 0.00V, max = + 0.00V) ALARM

+ 3.3V: + 0.93V (min = + 3.14V, max = + 3.46V) ALARM

+ 5V: + 5.11V (min = + 4.73V, max = + 5.24V)

+ 12V: + 4.56V (min = + 10.82V, max = + 13.19V) ALARM

-12V:-7.10V (min =-13.18V, max =-10.88V) ALARM

-5V:-1.93V (min =-5.25V, max =-4.75V) ALARM

V5SB: + 5.51V (min = + 4.73V, max = + 5.24V) ALARM

VBat: + 0.02V (min = + 2.40V, max = + 3.60V) ALARM

Fan1: 0 RPM (min = 2732 RPM, div = 2) ALARM

Fan2: 0 RPM (min = 0 RPM, div = 2)

Fan3: 0 RPM (min = 0 RPM, div = 2)

Temp1: + 38 "(high = + 50", hyst = + 45 ") sensor = thermistor

Temp2: + 33.5'(high = + 80', hyst = + 75') sensor = thermistor

Temp3: + 33.5'(high = + 80', hyst = + 75') sensor = thermistor

Vid: + 0.000 V (VRM Version 10.0)

Alarms:

Beep_enable:

Sound alarm enabled

Here we can see that the temperature does not correspond to the CPU, so we can mainly modify / etc/sensors.conf slightly, but we don't have to do it ourselves. Generally, we can download the configuration file from the motherboard manufacturer. Through lmsensors, we can get the information of motherboard temperature, CPU voltage and fan speed. We can use these data to monitor the operation of the system to prevent system problems.

Next, let's integrate it with MRTG.

[root@securitycn ~] # cd / usr/local/mrtg/bin

[root@securitycn ~] # vi temp.sh

# the content is as follows

#! / bin/bash

Cputemp= `/ usr/bin/sensors | grep temp1 | awk'{print $2}'| cut-c 2-4` # this sentence means to find the line with temp1 and print 2-4 words of the second column

Systemp = `/ usr/bin/sensors | grep temp2 | awk'{print $2}'| cut-c 2-5` need not be explained

Echo $cputemp

Echo $systemp

# the uptime

Uptime | sed's: ^. * up\ (. *\), [0-9] [0-9] * users.*$:\ 1up'

# my name

Uname-n

[root@securitycn ~] # chmod + x temp.sh changed to executable

[root@securitycn] # / temp.sh try to see if there is a problem

thirty-nine

33.5

15:36:19 up 22:28, 1 user, load average: 0.04, 0.09, 0.04

Securitycn

Let's write the following file.

[root@securitycn ~] # cd.. / etc/

[root@securitycn ~] # vi temp.cfg

WorkDir: / data1/usr/apache/htdocs/mrtg/temp/

Target [index]: `/ usr/local/mrtg/bin/ temp.sh`

MaxBytes [index]: 80

Options [index]: gauge, nopercent, growright

YLegend [index]: Temp (degrees)

ShortLegend [index]: degrees

LegendO [index]: system temperature

LegendI [index]: CPU temperature

Title [index]: system thermometer

PageTop [index]:

Main engine thermometer

[root@securitycn] # / usr/local/mrtg/bin/mrtg / usr/local/mrtg/etc/temp.cfg

If you execute it three times, you won't make a mistake.

Then add it to crontab.

* / 5 * / usr/local/mrtg/bin/mrtg / usr/local/mrtg/etc/temp.cfg consists of 2 pages.

This is the end of the content of "how to use the software lm_sensors to monitor Linux system and CPU temperature". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.