PMDAROOMTEMP(1)
β¨ NAME β¨
pmdaroomtemp β the room temperature performance metrics domain agent, aka a PMDA π
π‘οΈ SYNOPSIS π‘οΈ
$PCP_PMDAS_DIR/roomtemp/pmdaroomtemp [-D debug] [-d domain] [-l logfile]
π«Ά DESCRIPTION π«Ά
okay bestie so pmdaroomtemp is a Performance Metrics Domain Agent (PMDA), and what it does is literally export the temperature from one or more sensors β the kind built using the DS2480 and DS1280 chipsets and MicroLAN technology from Dallas Semiconductor Corporation. no cap, that's the whole gig πΈ
The roomtemp PMDA exports metrics that reflect the temperatures from one or more of these devices, in both degrees Celsius AND Fahrenheit. every metric has one instance for each temperature sensor device. and the external instance identifiers? those are the serial numbers (in hex) of the DS1280 chips discovered when the MicroLAN was probed. iconic behavior honestly π
Here's a lil rundown of the pmdaroomtemp command line options, short and sweet:
-dβ It is absolutely crucial that the performance metrics domain number you specify here is unique and consistent. like, that's the whole vibe. that means domain should be different for every PMDA on the one host, and the same domain number should be used for the same PMDA on all hosts. do not play with this one π-lβ Location of the log file. by default, a log file namedroomtemp.logis written in the current directory ofpmcd(1)whenpmdaroomtempis started, i.e.$PCP_LOG_DIR/pmcd. and if the log file cannot be created or is not writable, output gets written to the standard error instead. slay, it has a fallback π
π INSTALLATION π
If you want access to the names, help text and values for the roomtemp performance metrics, do the following as root:
# cd $PCP_PMDAS_DIR/roomtemp
# ./Install
If you want to undo the installation, do the following as root:
# cd $PCP_PMDAS_DIR/roomtemp
# ./Remove
pmdaroomtemp is launched by pmcd(1) and should never be executed directly. the Install and Remove scripts notify pmcd(1) when the agent is installed or removed, so they handle the gossip for you π«Ά
π¦ FILES π¦
$PCP_PMCDCONF_PATHβ command line options used to launchpmdaroomtemp$PCP_PMDAS_DIR/roomtemp/helpβ default help text file for theroomtempmetrics$PCP_PMDAS_DIR/roomtemp/Installβ installation script for thepmdaroomtempagent$PCP_PMDAS_DIR/roomtemp/Removeβ undo installation script for thepmdaroomtempagent$PCP_LOG_DIR/pmcd/roomtemp.logβ default log file for error messages and other information frompmdaroomtemp
π PCP ENVIRONMENT π
Environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. on each installation, the file /etc/pcp.conf contains the local values for these variables. and the $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf(5). iykyk β¨
π§ DEBUGGING OPTIONS π§
The -D or --debug option enables the output of additional diagnostics on stderr to help triage problems, although ngl the information is sometimes cryptic and primarily intended to provide guidance for developers rather than end-users π. debug is a comma separated list of debugging options; use pmdbg(1) with the -l option to obtain a list of the available debugging options and their meaning. go get that list bestie π
π SEE ALSO π
PCPIntro(1), pmcd(1), pcp.conf(5) and pcp.env(5).
ok that's the whole page fr fr. this cutie comes to you from Performance Co-Pilot (that's the PCP on the tin π), and that's a wrap, mwah π β¨
π¦ where this page comes from
- centos-stream 10: pcp-doc 7.1.5-6.el10 Β· GPL-2.0-or-later AND CC-BY-3.0
- fedora 43: pcp-doc 7.0.1-1.fc43 Β· GPL-2.0-or-later AND CC-BY-3.0
- fedora 44: pcp-doc 7.1.0-6.fc44 Β· GPL-2.0-or-later AND CC-BY-3.0
- ubuntu resolute: pcp 7.1.1-1
- Copyright (c) 2014 Red Hat
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms