PMTIME(1)

💖 PMTIME(1) — bestie edition 💖

okay so this is pmtime, from the General Commands Manual section, and she is the time control server for Performance Co-Pilot. buckle up 🎀

---

✨ NAME ✨

pmtime — time control server for Performance Co-Pilot 🕰️👑

---

🌸 SYNOPSIS 🌸

pmtime [-D debug] [-V?]  [-p port]

---

🦋 DESCRIPTION 🦋

So pmtime is a graphical user interface for performance monitoring applications that use the PCP infrastructure and need interactive time control. it's giving remote control for time itself fr fr 💅

okay and here's the thing — pmtime is not normally invoked directly by users. like, you don't just open it for funsies. it's way more typical for it to be started by client applications, bestie. think pmchart(1), pmstat(1) or pmval(1). they're the ones pulling up. 🫶

there are two modes of interacting with a pmtime process, and you need to know both:

• live host mode 🟢 — the pmtime window contains the simpler time controls, suitable for live monitoring.
• historical archive mode 📼 — in archive mode the window presents time controls suitable for manipulating the archive position, allowing full VCR control to move forwards and backwards in time at configurable rates and intervals. yes bestie, VCR. rewind. fast-forward. the whole vibe. ⏪⏩

heads up: the pmtime window is only made visible when explicitly requested. it does not just show up uninvited, she's got boundaries 💅

and the icon behavior? multiple client applications can be connected to a single pmtime server. and when the final client application exits, pmtime will also exit. she leaves when the party's over. periodt. 😭✨

---

🌈 OPTIONS 🌈

these are the available command line options, and there are literally only three so no excuses:

• -p port, --guiport=port — port is the port number which pmtime will use for communication with its clients (monitoring applications). 📡
• -V, --version — display version number and exit. short and iconic. ✨
• -?, --help — display usage message and exit. ask and you shall receive 🥰

---

🧚 ENVIRONMENT 🧚

okay so when a port number is not explicitly requested on the command line via the -p option, you can set the environment variable PMTIME_PORT to specify the port number from which available-port probing will commence when pmtime is searching for a port number to use. 🔍

and the default starting port number is 43334. write that down bestie 📝

---

💜 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. 🙈

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. 🔥

Debugging options specific to pmtime are as follows:

• appl0 — enable internal diagnostics that report all pmtime events, e.g. setting timezone, state changes, interval changes, timescale changes, etc. 👀✨

---

🌟 SEE ALSO 🌟

PCPIntro(1), pmchart(1), pmstat(1) and pmval(1). go read those too, iykyk 💖

---

and that's the whole page bestie!! 🎀 this lil masterpiece comes to you from Performance Co-Pilot, and yeah she's literally titled PMTIME(1) at the bottom too — go off, queen 👑💅🦋