Difference between revisions of "Package:Lm sensors"

From Funtoo
Jump to navigation Jump to search
(notice about configuration)
Line 7: Line 7:
== Introduction==
== Introduction==
<code>lm_sensors</code> is a free and open-source application that provides tools and drivers for monitoring temperatures, voltage, and fans. This document explains how to install, configure, and use lm_sensors.
<code>lm_sensors</code> is a free and open-source application that provides tools and drivers for monitoring temperatures, voltage, and fans. This document explains how to install, configure, and use lm_sensors.
== Configuration ==
The <code>lm_sensors</code> service needs configuration in the <code>/etc/conf.d/lm_sensors</code> file, which doesn't exists by default and can be generated by running the <code>sensors-detect</code> tool. This tool will try to identify the kernel's modules needed by sensors and then place them into configuration file to be loaded/unloaded when the service starts/stops.
Beware, when some of these modules are loaded when the tool starts (e.g. from <code>/etc/conf.d/modules</code> or manually) , they will not added into configuration file. When the modules are loaded manually, the result can be, that they will not be loaded on next system (re)start.
{{EbuildFooter}}
{{EbuildFooter}}

Revision as of 17:26, June 9, 2016

Lm sensors

   Tip

We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.

Introduction

lm_sensors is a free and open-source application that provides tools and drivers for monitoring temperatures, voltage, and fans. This document explains how to install, configure, and use lm_sensors.

Configuration

The lm_sensors service needs configuration in the /etc/conf.d/lm_sensors file, which doesn't exists by default and can be generated by running the sensors-detect tool. This tool will try to identify the kernel's modules needed by sensors and then place them into configuration file to be loaded/unloaded when the service starts/stops.

Beware, when some of these modules are loaded when the tool starts (e.g. from /etc/conf.d/modules or manually) , they will not added into configuration file. When the modules are loaded manually, the result can be, that they will not be loaded on next system (re)start.