PMLOGGER_REWRITE(1)

💖 PMLOGGER_REWRITE 💖

okay bestie, so this is a page from the General Commands Manual for PCP (that's Performance Co-Pilot, the whole vibe), and the star of the show is pmlogger_rewrite. sit down, grab a boba, we're doing archive glow-ups today 🦋

---

✨ NAME ✨

pmlogger_rewrite — the little helper script whose entire job is rewriting Performance Co-Pilot archives. that's it. that's the girl. 💅

---

✨ SYNOPSIS ✨

$PCP_BINADM_DIR/pmlogger_rewrite [-dNsVvw?]  [-c config] archive ...

---

✨ DESCRIPTION ✨

so, pmlogger_rewrite is a helper script that pmlogger_daily(1) calls up when it needs to rewrite Performance Co-Pilot (PCP) archives. why do archives need a rewrite, you ask? because metadata evolves, babes. it's giving ✨growth✨. rewriting lets old archives get updated so they can then be merged with the current archives. no cap.

pmlogger_rewrite is a wrapper script for pmlogrewrite(1), and it will potentially rewrite all of the archives matching the archive arguments. obsessed. so what even counts as an archive argument? any of these:

• a PCP archive file name 📁
• the basename for the files in a PCP archive
• a directory — in which case all subordinate PCP archives are found by recursive descent 🧚

and here's the tea: pmlogrewrite gets run with the -i option, so rewriting happens "in place". the -q option is also used, so if no rewriting is actually required, then no changes are made to the archive files. respectful king behavior honestly. 👑

---

✨ OPTIONS ✨

first up, these options get passed straight through to pmlogrewrite: -c (or --config), -d (or --desperate), -s (or --scale), -v (or --verbose) and -w (or --warnings). for what they actually mean, go read pmlogrewrite(1) — that's the source of truth, bestie, I'm not making stuff up here. 📖

and the remaining options, aka the ones that belong to this script:

• -N, --showme — runs pmlogger_rewrite in a "show me" or "dry run" mode where the tasks that would be performed get reported, but no changes are made. typically used for debugging, and usually paired with one -V (verbose) or two -V options (very verbose). it's the "let me see the fit before I buy it" option fr fr. 🙈
• -V, --verbose — increases script output verbosity. more V's, more words. 🗣️
• -?, --help — displays the usage message and exits. bye bestie 🫶

---

✨ 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. and the $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf(5). so like, if you need to point things somewhere else, that's your girl. 🌸

---

✨ SEE ALSO ✨

PCPIntro(1), pmlogger(1), pmlogger_daily(1) and pmlogrewrite(1). the whole friend group, go say hi. 💜

---

and that's the page, babe!! this came to you courtesy of Performance Co-Pilot (that's the PCP in the corner, version vibes and all) — go forth and rewrite those archives, you absolute icon ✨🎀💅