Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

psensor-server(1) [debian man page]

PSENSOR-SERVER(1)						   User Commands						 PSENSOR-SERVER(1)

NAME
psensor-server - Temperature and system monitoring Web server SYNOPSIS
psensor-server [OPTION]... DESCRIPTION
psensor-server is an HTTP server for monitoring hardware sensors remotely. It provides a JSON Web service which can be used by psensor(1) to monitor remotely the hardware sensors of a computer. It can provide information about: * the temperature of the motherboard and CPU sensors (using lm-sensors). * the temperature of the Hard Disk Drives (using hddtemp). * the rotation speed of the fans (using lm-sensors). It is also possible to connect to the psensor-server with a browser, a simple Web page is displaying the sensors information and the CPU usage. The URL http://hostname:3131/api/1.0/sensors/[id] returns a JSON object containing all information about a sensor. [id] is the uniq identi- fier of the sensor. Here is an example of the JSON object of type 'sensor': { "id": "lmsensor acpitz-virtual-0 temp1", "name": "temp1", "type": 257, "min": 47.800000, "max": 60.800000, "measures": [ { "value": 47.800000, "time": 1311374873 }, { "value": 49.800000, "time": 1311374878 }, { "value": 49.800000, "time": 1311374883 } ], "last_measure": { "value": 49.800000, "time": 1311374883 } } Fields of the type 'sensor': * id: the uniq identifier of the sensor. * name: a humean readable name of the sensor (might not be uniq). * type: the type of sensor. Look at src/lib/psensor.h for the different types. * min: the minimal value of the sensor. * max: the maximal value of the sensor. * measures: all measures of the sensor. * last_measure: the last value of the sensor. * time: the time of a measure as the number of seconds since 1970/01/01. The URL http://hostname:3131/api/1.0/sensors returns a JSON array containing all JSON objects of type 'sensor'. If run in debug mode, psensor-server can be stopped by sending an HTTP request with the URL 'http://hostname:port/api/1.0/server/stop'. OPTIONS
-h, --help display this help and exit -v, --version display version information and exit -d,--debug run in debug mode -p,--port=PORT webserver port -w,--wdir=DIR directory containing webserver pages WARNING
psensor-server does not provide any way to restrict the connection to the HTTP server, worst, no effort has been made against malicious HTTP attacks. You should make the psensor-server port available only to a network or computer you trust by using the usual network secu- rity tools of the system (for example, iptables(8) ). REPORTING BUGS
Report bugs to: jeanfi@gmail.com psensor home page: <http://wpitchoune.net/psensor> COPYRIGHT
Copyright (C) 2010-2012 jeanfi@gmail.com License GPLv2: GNU GPL version 2 or later <http://www.gnu.org/licenses/old-licenses/gpl-2.0.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. SEE ALSO
psensor(1), sensors(1), sensors-detect(8) psensor-server 0.6.2.17 March 2012 PSENSOR-SERVER(1)

Check Out this Related Man Page

AIBS(4) 						   BSD Kernel Interfaces Manual 						   AIBS(4)

NAME
aibs -- ASUSTeK AI Booster ACPI ATK0110 voltage, temperature and fan sensor SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device acpi device aibs Alternatively, to load the driver as a module at boot time, place the following lines in loader.conf(5): acpi_load="YES" aibs_load="YES" DESCRIPTION
The aibs driver provides support for the voltage, temperature and fan sensors available through the ATK0110 ASOC ACPI device on ASUSTeK moth- erboards. The number of sensors of each type, as well as the description of each sensor, varies according to the motherboard. The driver supports an arbitrary set of sensors, provides descriptions regarding what each sensor is used for, and reports the current values as well as the supposed range specifications of each sensor's input as defined by the motherboard manufacturer through ACPI. The range specifications are as follows: o Voltage sensors have a lower and an upper range specification. o Temperature sensors have two upper specifications. o Fan sensors may either have only the lower specification, or, depending on the DSDT, one lower and one upper specification. Sensor readings and the range specifications are made available through the sysctl(3) interface, and can be monitored with sysctl(8). For example, on an ASUS V3-P5G965 barebone: > sysctl dev.aibs.0.{volt,temp,fan} dev.aibs.0.volt.0: 1192 850 1600 dev.aibs.0.volt.1: 3312 2970 3630 dev.aibs.0.volt.2: 5017 4500 5500 dev.aibs.0.volt.3: 12302 10200 13800 dev.aibs.0.temp.0: 28.0C 80.0C 95.0C dev.aibs.0.temp.1: 55.0C 60.0C 95.0C dev.aibs.0.fan.0: 878 600 7200 dev.aibs.0.fan.1: 0 700 7200 > sysctl -d dev.aibs.0.{volt,temp,fan} dev.aibs.0.volt: dev.aibs.0.volt.0: Vcore Voltage dev.aibs.0.volt.1: +3.3 Voltage dev.aibs.0.volt.2: +5 Voltage dev.aibs.0.volt.3: +12 Voltage dev.aibs.0.temp: dev.aibs.0.temp.0: CPU Temperature dev.aibs.0.temp.1: MB Temperature dev.aibs.0.fan: dev.aibs.0.fan.0: CPU FAN Speed dev.aibs.0.fan.1: CHASSIS FAN Speed Generally, sensors provided by the aibs driver may also be supported by certain other drivers or utilities that access the ISA / LPC or I2C / SMBus devices directly. The precise collection of aibs sensors is comprised of the sensors specifically utilised in the motherboard design, which may be supported through a combination of one or more physical hardware monitoring chips. The aibs driver, however, provides the following advantages when compared to the native hardware monitoring drivers or other utilities: o Sensor values from aibs are expected to be more reliable. For example, voltage sensors in many hardware monitoring chips can only sense voltage from 0 to 2 or 4 volts, and the excessive voltage is removed by the resistors, which may vary with the motherboard and with the voltage that is being sensed. In aibs, the required resistor factors are provided by the motherboard manufacturer through ACPI; in the native drivers, the resistor factors are encoded into the driver based on the chip manufacturer's recommendations. In essence, sensor values from aibs are very likely to be identical to the readings from the Hardware Monitor screen in the BIOS. o Sensor descriptions from aibs are more likely to match the markings on the motherboard. o Sensor range specifications are supported by aibs. The range specification is reported for each individual sensor as suggested by the motherboard manufacturer. For example, the threshold for the CPU temperature sensor is likely to be significantly higher than that for the chassis temperature sensor. o Support for newer chips in aibs. Newer chips may miss a native driver, but should be supported through aibs regardless. SEE ALSO
sysctl(3), acpi(4), sysctl(8) HISTORY
The aibs driver first appeared in OpenBSD 4.7, DragonFly 2.5, NetBSD 6.0 and FreeBSD 9.0. An earlier version of the driver, acpi_aiboost, first appeared in FreeBSD 7.0 and NetBSD 5.0. AUTHORS
The aibs driver was written for OpenBSD, DragonFly, NetBSD and FreeBSD by Constantine A. Murenin <cnst@FreeBSD.org>, Raouf Boutaba Research Group, David R. Cheriton School of Computer Science, University of Waterloo. An earlier version of the driver, named acpi_aiboost, was written for FreeBSD by Takanori Watanabe. BSD
April 4, 2010 BSD
Man Page