Free system sensor software for linux

System-CoW is a system monitoring SuperKaramba theme.

You must have installed hddtemp and all i2c sensors in kernel to have this script working!

You must launch:

hddtemp -d /dev/hd[abc] // if you have 3 disks!

to have temperature working!

For gentoo add a line to /etc/conf.d/local.start to load the command line at startup!

compact system monitor is a small and compact system monitor for SuperKaramba.

Credit where credit is due, i think i stole the icons from Borealis? Nice are they not? And the idea from someone else.

The theme can be changed somewhat by editing the theme and comenting out some lines.

Hope you like it! Its my first!

XMLSensors is a set of programs that serve as generic plugins to monitoring systems such as Nagios, Big Brother, Zabbix, and many others. The sensors output an XML status file for each sensor that is retrieved and processed by a generic plugin to the monitoring system of your choice.
The XML can be published on a Web server, and transferred via network shares or SSH. It currently has 2 sensors. phpbb2_version checks the version of a phpBB forum against the offcial release, and smf_version does the same for a Simple Machines forum. Theres also a dummy sensor that you can modify yourself.
It contains the following sensors:
- dummy (an empty sensor you can modify)
- phpbb_version - Checks the version on phpbb2 sites against the current version on phpbb.com
- smf_version - Check the version of Simple Machines forums against the current version on the official site.
Enhancements:
- This release adds support for the XMLSensor1.1 format and moves to the GPLv3.

Sensors is a SuperKaramba theme for motherboard sensors monitoring.

This is my first upload on to KDE-look its a very basic sensor Karamba theme. Since I like to know what my computer is doing all the time.

Sensors theme uses LM-sensors and this must be installed before this theme will work. Also you may need to edit the .theme file to fit your computers layout. any problems, thoughts concerns or even pointers would be greatly appreciated.

check_lm_sensors is a Nagios plugin to monitor the values of on-board sensors and hard disk temperatures on Linux systems.
Usage:
-h, --help help
-c, --check specifies a sensor along with warn and crit values
-c fan1=1000,2000 checks if fan1 is above 1000 or 2000
-c vcore=1,2,12 checks if vcore is between 11-13 or 10-14 (12+-value)
sensors with a space in the name can be specified
- by escaping the space --check sda Temp=50,60
- by quoting the name --check sda Temp=50,60
- by substituting the space by an underscore --check sda_Temp=50,60
-d, --drive check drive temperature
-l, --list list sensors
--hddtemp_bin specifies the location of the hddtemp binary
--sensors_bin specified the location of the sensors binary
-v, --verbose verbose output
--version prints $prog_names version and exits
Example:
$ ./check_lm_sensors -v -c sda Temp=30,5,10 -c +2.5V=0.2,0.3,2.5
found sensor +3.3V (3.39)
found sensor +2.5V (2.39)
found sensor VCore (1.19)
found sensor +5V (4.61)
found sensor +12V (11.96)
found sensor +3.3V (3.23)
found sensor Case Fan (0)
found sensor CPU Fan (0)
found sensor CPU Temp (62.1)
found sensor Int Temp (66.0)
found sensor vid (1.250)
found temperature for drive sda (51)
LM_SENSORS CRITICAL sda Temp=51|Case Fan=0;;;; vid=1.250;;;; +5V=4.61;;;; +2.5V=2.39;;;; Int Temp=66.0;;;; +12V=11.96;;;; +3.3V=3.23;;;; VCore=1.19;;;; CPU Temp=62.1;;;; CPU Fan=0;;;; sda Temp=51;;;;
Enhancements:
- --low, --high, and --range options were added.
- The --check option was deprecated.
- The sensor(s) output were added to the status string.
- Automatic detection of the path was implemented for hddtemp and sensors. --nosensors and --nodrives options were added for disabling sensors or driving temperature checks.
- A --rename option renames sensors.
- Only the checked sensors are included in the performance output.
- A --sanitaze option removes spaces from sensor names.

Wmsensormon is a doc app for WindowMaker that utilizes lm_sensors to monitor CPU temp, sys temp, fan speeds, and CPU voltage.
It offers configurable warnings for overheating, and the sensors displayed are adjustable by the user with command line parameters.
Installation:
make
make install
wmsensormon
Options:
-h, --help this help screen
-v, --version print version information
-f show temperatures in Fahrenheit
-s default SMP mode (mode #1)
-s1 SMP mode #1 (CPU 1, CPU 2, sys, fan)
-s2 SMP mode #2 (CPU 1, CPU 2, fan 1, fan 2)
-sw switch CPU and SYS temperature readings
use with -s1 or -s2 if SYS temp is first
-swf switch fans to read fan3 and fan4
-r refresh time (in microseconds, default 100000)
-l enable logging with default time, (default 30000)
-ln enable logging with specified time, (1000 = 1 min)
-dt danger CPU temperature, default: system value (i.e. 60)
input values in Celsius
-ds danger SYS temperature, default: system value (i.e. 60)
input values in Celsius
-df danger fan speed, default: system value (i.e. 3000)
-wt warning CPU temperature, default: danger value
input values in Celsius
-ws warning SYS temperature, default: danger value
input values in Celsius
-wf warning fan speed, default: danger value
-lv limit CPU core volts, default is system value either: max voltage first, min
voltage second (i.e. 180 170) or:
percent difference first, value second (i.e. % 5 175)
Enhancements:
- when a command line arg gets a invalid parameter return error rather than ok
- fixed reading in the limit values from the wrong sensor if using the -sw option
- added option to choose a sensors chip to read from.
- added support for detecting whether the chosen sensor chip is a temperature sensor or some other type.
- if the choosen chip is number 0 or no chip is chosen, autodetect the chip to use.

TyopoytaORvelo System MOnitor is a system monitor for Linux that sits in the corner of your desktop. TyopoytaORvelo System MOnitor renders itself on the root window (on the desktop) or to its own transparent window any special eyecandy.
TyopoytaORvelo System MOnitor can show lots of info about your system, including:
- kernel version
- uptime
- network interface information
- memory and swap usage
- hostname
- machine, i686 for example
- system name, Linux for example
- temperatures from i2c-sensors
Installation:
The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation.
It uses those values to create a `Makefile in each directory of the package. It may also create one or more `.h files containing system-dependent definitions.
Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, a file `config.cache that saves the results of its tests to speed up reconfiguring, and a file `config.log containing compiler output (useful mainly for debugging `configure).
If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.
If at some point `config.cache contains results you dont want to keep, you may remove or edit it.
The file `configure.in is used to create `configure by a program called `autoconf. You only need `configure.in if you want to change it or regenerate `configure using a newer version of `autoconf.
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute
`configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.
There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.