PMERR(1)

✨ NAME ✨

pmerr — the little glow-up translator that turns Performance Co-Pilot error codes into actual readable error messages 💖

🌸 SYNOPSIS 🌸

pmerr [-?] code ...
pmerr -l

🦋 DESCRIPTION 🦋

okay bestie, so picture this: PCP hits you with a raw error code and you're just standing there like 🧍‍♀️. pmerr</pmerr> is here to fix that. It takes standard Performance Co-Pilot (PCP) error codes through the code argument(s) and hands you back the corresponding error text. literally a translator for your terminal, no cap 💅

Each code can be any of these three vibes:

• a plain integer
• a hexadecimal value
• a hexadecimal value with either 0x or 0X out front

🚨 IMPORTANT VIBE CHECK: error codes must be less than zero. So if you feed it a positive number, it'll throw a warning message at you and then use the negated value instead. yes, it's doing math on your mistakes. iconic.

🎀 OPTIONS 🎀

Here's the lineup, bestie:

• -l, --list — this alternative invocation makes all known error codes get listed out, along with their symbolic names AND their error text. it's giving full inventory 📋✨
• -?, --help — shows you the usage message and then exits. the classic "wait how do I use this" button 🫶

🌈 PCP ENVIRONMENT 🌈

So, environment variables with the prefix PCP_ are the ones used to parameterize the file and directory names that PCP uses. 💜

On each installation, the file /etc/pcp.conf contains the local values for these variables. 📁

And the $PCP_CONF variable? You can use it to point at an alternative configuration file instead — as described in pcp.conf(5). slay, customizable 🧚

👑 SEE ALSO 👑

PMAPI(3), pmErrStr(3), pcp.conf(5) and pcp.env(5) — go read those too, iykyk 💖

Performance Co-Pilot · PCP · PMERR(1)

and that's the whole page bestie, mwah 💋 go translate some error codes, you absolute main character 🦋💅✨