PMDAMOUNTS(1)

💖 PMDAMOUNTS(1) — the glow-up edition 💖

okay so you're reading the manual page for pmdamounts, and it lives in the General Commands Manual section. She's a Performance Co-Pilot girlie, bestie, and she's here to tell you whether your filesystems are up or down. 🦋

---

✨ NAME ✨

pmdamounts</purl> — the filesystem mounts performance metrics domain agent, aka PMDA. That's literally her whole job title and she's serving it. 💅

---

🌸 SYNOPSIS 🌸

$PCP_PMDAS_DIR/mounts/pmdamounts [-D debug] [-d domain] [-l logfile] [-U username]

no cap, that's the whole invocation. Four little options, one big vibe. ✨

---

👑 DESCRIPTION 👑

pmdamounts is a simple Performance Metrics Domain Agent — a PMDA — whose whole thing is monitoring the availability of a given set of filesystem mounts. That's it. That's the assignment. 🫶

The mounts PMDA exports metrics that reflect whether the configured filesystems are mounted (that's "up") or not. The list of mount points to monitor is specified via the $PCP_PMDAS_DIR/mounts/mounts.conf file, which is honestly so chill — it just contains one line for each mount point. Simple. Iconic. No drama. 🌈

A brief description of the pmdamounts command line options follows, and yes bestie, we're going through every single one:

• -d — listen closely because this one MATTERS: it is absolutely crucial that the performance metrics domain number specified here is unique and consistent. Like, that's the whole rule. The 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. Consistency is the main character here. 👑
• -l — where the log file goes. By default, a log file named mounts.log is written in the current directory of pmcd(1) when pmdamounts is started, i.e. $PCP_LOG_DIR/pmcd. And heads up: if the log file cannot be created or is not writable, output is written to the standard error instead. She'll find a way to be heard. 😭
• -U — the user account under which to run the agent. The default is the unprivileged "pcp" account in current versions of PCP, but in older versions the superuser account ("root") was used by default. So like, generational difference, iykyk. 💜

---

🎀 INSTALLATION 🎀

If you want access to the names, help text and values for the mounts performance metrics, do the following as root:

# cd $PCP_PMDAS_DIR/mounts
# ./Install

If you want to undo the installation, do the following as root:

# cd $PCP_PMDAS_DIR/mounts
# ./Remove

pmdamounts is launched by pmcd(1) and should never be executed directly. not me running it myself — do NOT do that, bestie, it's giving chaos. 🙈

The Install and Remove scripts notify pmcd(1) when the agent is installed or removed, so the communication is handled. She's a good friend like that. 🫶

---

🦋 FILES 🦋

• $PCP_PMCDCONF_PATH — command line options used to launch pmdamounts
• $PCP_PMDAS_DIR/mounts/help — default help text file for the mounts metrics
• $PCP_PMDAS_DIR/mounts/Install — installation script for the pmdamounts agent
• $PCP_PMDAS_DIR/mounts/Remove — undo installation script for the pmdamounts agent
• $PCP_LOG_DIR/pmcd/mounts.log — default log file for error messages and other information from pmdamounts

the way that every single one of these is documented… we love a thorough queen. ✨

---

🌈 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. The $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf(5). config files are self care, periodt. 💜

---

💀 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 for end-users. So like, it's giving insider info. 🤫

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). the friend group fr fr. 🫶

---

okay that's the whole page!! 💖

This one came to you from Performance Co-Pilot — that's the PCP of it all — under the name PMDAMOUNTS(1). mwah, go check your mounts, ily 💅✨