PMPOST(1)

💌 PMPOST(1) — bestie edition 🎀

okay so real quick, the manual name for this one is General Commands Manual and the command itself is pmpost. yes we're doing this, and yes it's gonna be iconic.

---

✨ NAME ✨

pmpost — appends messages to the Performance Co-Pilot notice board. that's the whole job. it's giving "sticky note on the fridge but make it enterprise" 💖

---

🌸 SYNOPSIS 🌸

$PCP_BINADM_DIR/pmpost [-D debug] message

one message, one command, no cap. literally that's it.

---

🦋 DESCRIPTION 🦋

okay so here's the tea. pmpost takes your text message and appends it to the very end of the Performance Co-Pilot (PCP) notice board file, which lives at $PCP_LOG_DIR/NOTICES. and it does this atomically — meaning it guards against the notice board file getting corrupted when multiple invocations of pmpost happen at the same time. no race conditions, no messy file, we stay safe and cute 💅

the PCP notice board itself is meant to be a persistent store and a clearing house for important messages relating to the operation of the PCP, plus the notification of performance alerts from pmie(1) — specifically for when those other notification options are either unavailable or just... not it. unsuitable, as the professionals say 🙈

before anything gets written, messages get prefixed with the current time. and when the current day is different from the last time the notice board file was written, pmpost will also prepend the message with the full date. so your timeline stays chronological, as it should 👑

if the notice board file doesn't exist, pmpost will create it. no drama. pmpost would usually run from long-running PCP daemons executing under the (typically unprivileged) $PCP_USER and $PCP_GROUP accounts. the file should be owned and writable by the $PCP_USER user, and readable by others — sharing is caring fr fr 🫶

---

📁 FILES 📁

• $PCP_LOG_DIR/NOTICES — the PCP notice board file. this is the one. the main character. the whole point 🌟

---

🌈 PCP ENVIRONMENT 🌈

the file /etc/pcp.conf contains the local values for the PCP_ variables. that's where the vibes get configured, bestie.

---

🐧 UNIX SEE ALSO 🐧

logger(1).

---

🪟 WINDOWS SEE ALSO 🪟

pcp-eventlog(1).

---

🎀 DEBUGGING OPTIONS 🎀

the -D or --debug option enables the output of additional diagnostics on stderr, to help triage problems. lowkey the information is sometimes cryptic though, and it's primarily intended to provide guidance for developers rather than for end-users. so like, it's not for everyone, iykyk.

debug is a comma separated list of debugging options. use pmdbg(1) with the -l option to get a list of the available debugging options and what they mean. go off, go find out 🔍

---

💜 SEE ALSO 💜

pmie(1), pcp.conf(5) and pcp.env(5).

ngl bestie, if you got this far you should probably also read those. they're the supporting cast and they ate 💅

---

and that's the whole page!! brought to you by Performance Co-Pilot, from the PCP collection — PMPOST(1), the notice board icon we all needed 🫶✨