PMDALMSENSORS(1)

πŸ“¦
version 7.2.2 Β· 3 versions
, in arch rolling, centos-stream 10, centos-stream 9, debian trixie, fedora 43, fedora 44, ubuntu questing, ubuntu resolute, ubuntu stonking

πŸ’– pmdalmsensors(1) β€” bestie edition πŸ’–

okay so. this is the manual page for pmdalmsensors, and yeah the whole "PMDALMSENSORS(1)" thing at the top is just the fancy man-page name tag, but we're not doing that, we're doing this instead. sit down, grab a strawberry, let's go πŸ“


✨ NAME ✨

pmdalmsensors β€” Linux hardware monitoring performance metrics domain agent (PMDA)

like. it's a PMDA. a Performance Metrics Domain Agent. for Linux hardware monitoring. that's the whole vibe πŸ’…


✨ SYNOPSIS ✨

$PCP_PMDAS_DIR/lmsensors/pmdalmsensors [debug]

yeah. that's it. that's the whole invocation. [debug] is optional, she's chill like that 🫢


🌸 DESCRIPTION 🌸

so pmdalmsensors is a Performance Metrics Domain Agent (PMDA) and what she does is extract performance metrics describing the state of hardware using the lm-sensors software on compatible motherboards. compatible is doing a LOT of work in that sentence ngl 😭

and the lmsensors PMDA exports metrics that measure fan speeds and core temperatures. that's it. that's her whole job. iconic honestly. your fans and your cores. she's watching them. always. πŸ‘€


🌈 INSTALLATION 🌈

okay bestie, if you want access to the names, the help text and the values for the lmsensors performance metrics, you gotta do this as root:

# cd $PCP_PMDAS_DIR/lmsensors
# ./Install
yes. root. I said what I said. πŸ‘‘

and if you want to undo the installation (no judgement, we've all been there), do this as root:

# cd $PCP_PMDAS_DIR/lmsensors
# ./Remove

now. important lore: pmdalmsensors.python is usually launched by pmcd(1), and not executed directly. running it by hand is mostly a debugging thing, iykyk πŸ”

and the Install and Remove scripts? they notify pmcd(1) when the agent is installed or removed. they keep pmcd in the loop. communication. we love to see it πŸ’–


πŸ’… OPTIONS πŸ’…

so pmdalmsensors.python supports the following options. here we go:

  • -i, --inject β€” inject data from file instead of using sensors. fake it till you make it, but like, on purpose, for testing πŸ§ͺ
  • -d, --debug β€” debug level: 0 (default), 1 or 2. zero is the default bestie, that's the "I'm fine" setting ✨
  • -h, --help β€” show a help message. she will explain herself. slay.

and here's a lil tip for when pmdalmsensors.python is being run from PMCD but you still want options: you might want to use 'args' in the 'Install' script, for example

args="-i /path/static_sensors_output.txt"

periodt. that's the move. πŸŽ€


πŸ¦‹ FILES πŸ¦‹

  • $PCP_PMCDCONF_PATH β€” command line options used to launch pmdalmsensors
  • $PCP_PMDAS_DIR/lmsensors/help β€” default help text file for the lmsensors metrics
  • $PCP_PMDAS_DIR/lmsensors/Install β€” installation script for the pmdalmsensors agent
  • $PCP_PMDAS_DIR/lmsensors/Remove β€” undo installation script for the pmdalmsensors agent

look at her. organized. labeled. a whole queen with a whole file structure πŸ‘‘


🌟 PCP ENVIRONMENT 🌟

so here's the tea: environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. fancy word, means they fill in the blanks ✨

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). options! choices! main character energy 🌈


πŸ’œ SEE ALSO πŸ’œ

go read them. they're the supporting cast but they matter 🫢


and that's the whole page, bestie!! this lil manual came to you courtesy of Performance Co-Pilot (that's the source, that's the version tag, that's the whole house 🏠) and she's filed under PCP, and the footer date stamp is just… whenever you're reading this, honestly. timeless. iconic. no cap. πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from