PCP.ENV(5)

💖 pcp.env — the PCP vibe-setting script 💖

okay so this is PCP.ENV(5), from the File Formats Manual section, and it's literally the little script that gets Performance Co-Pilot's run-time environment variables all set up and cozy. bestie, it's giving backstage pass energy ✨

---

🎀 NAME 🎀

pcp.env — script to set Performance Co-Pilot run-time environment variables

---

🌸 SYNOPSIS 🌸

/etc/pcp.env

---

✨ DESCRIPTION ✨

So the pcp.env script gets sourced by assorted Performance Co-Pilot (PCP) scripts and utilities to define the PCP operating environment variables. That's its whole job, and it eats every time. 💅

The conjugate for executable programs that use the PCP libraries is the pmGetConfig(3) function — iykyk, that's the C-side twin. 🫶

Typical usage of pcp.env in a script is as follows:

#! /bin/sh

# source the PCP environment variables
. /etc/pcp.env
rest of script ...

The full syntax and semantics of the pcp.conf file and the pmGetConfig function are described in their respective reference pages — go read those if you want the deep lore 📚

If the file $HOME/.pcp/pcp.conf exists then this will be processed after the system-wide pcp.conf file. This provides a mechanism to selectively modify or augment the environment settings for PCP scripts, which maybe useful if the scripts are run with sudo(1) — because sudo(1) cleans the environment of important settings that are required to ensure the correct execution of the PCP scripts, e.g. $PATH or $PERL5LIB. not sudo being the messy one that wipes your whole setup 😭 no cap, your home config is the comeback.

---

🌈 ENVIRONMENT 🌈

• PCP_CONF — specifies an alternative path to the pcp.conf file. main character override behavior, fr fr 👑

---

💜 SEE ALSO 💜

PCPIntro(1), sudo(1), PCPIntro(3), PMAPI(3), pmGetConfig(3) and pcp.conf(5).

---

quick vibe check bestie: this page comes from Performance Co-Pilot, the PCP collection, page PCP.ENV(5) — that's the source and version tag, slay. 🌟

mwah, that's the whole page, you ate it, periodt 💖🦋🌸