PCP-UPTIME(1)
π PCP-UPTIME(1) π
okay bestie, so this is a page from the Performance Co-Pilot manual (that's the PCP thing, we'll get to it) and it's literally just pcp-uptime β the lil glow-up of the classic uptime command. sit down, grab a strawberry drink π, and let's get into it.
β¨ NAME β¨
pcp-uptime β tell how long the system has been running π°οΈ
like, "how long has this machine been awake, no nap, no cap."
πΈ SYNOPSIS πΈ
pcp [pcp options] uptime [-V?]
that's it. that's the whole vibe. π«Ά
π¦ DESCRIPTION π¦
pcp-uptime gives you a one line display of the following tea β:
- the current time β°
- how long the system has been running (the uptime, the main character stat)
- how many users are currently logged on π₯
- the system load averages for the past 1, 5, and 15 minutes π
and when you invoke it via the pcp(1) command, a whole little squad of pcp options becomes indirectly available to you: -h/--host, -a/--archive, -O/--origin, -Z/--timezone, and several other pcp options. so like, you get the group chat, not just the DM. π
π OPTIONS π
the available command line options are, in order, no skips:
-V,--versionβ display version number and exit. that's it, that's the whole job, bye π-?,--helpβ display usage message and exit. your lil instruction manual moment π
β οΈ okay so important one, listen up: when you're replaying from an archive using the-aoption, the required information may not be available at the default starting time. in which case the reported values will be?. like, question marks. the drama π. in that case, use the-Sor-Ooptions to move the starting time into a point in the archive where the required information is available. problem solved, slay. β¨
π NOTES π
pcp-uptime is inspired by the uptime(1) command and aims to be command line and output compatible with it. so it's giving homage, not reinvention. iconic behavior honestly π
π PCP ENVIRONMENT π
environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. very "everything is configurable, as it should be."
on each installation, the file /etc/pcp.conf contains the local values for these variables. π
the $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf(5). so if you wanna be different, you can be different. π
for environment variables affecting PCP tools, see pmGetOptions(3).
π SEE ALSO π
PCPIntro(1), pcp(1), uptime(1) and environ(7).
go read them, they're all in the friend group. π«Ά
and that's the whole page, bestie!! π this was PCP-UPTIME(1) from the Performance Co-Pilot (PCP) manual, and this specific page is dated with that same PCP release energy. mwah, go check your uptime, ily πβ¨
π¦ where this page comes from
- arch rolling: pcp 7.2.2-2 Β· GPL-2.0-or-later AND LGPL-2.1-or-later AND CC-BY-3.0
- centos-stream 10: pcp-doc 7.1.5-6.el10 Β· GPL-2.0-or-later AND CC-BY-3.0
- fedora 43: pcp-doc 7.2.1-1.fc43
- fedora 43: pcp-doc 7.2.2-1.fc43
- fedora 43: pcp-doc 7.2.2-2.fc43 Β· GPL-2.0-or-later AND CC-BY-3.0
- fedora 44: pcp-doc 7.1.0-6.fc44 Β· GPL-2.0-or-later AND CC-BY-3.0
- fedora 44: pcp-doc 7.2.1-1.fc44
- fedora 44: pcp-doc 7.2.2-1.fc44
- fedora 44: pcp-doc 7.2.2-2.fc44 Β· GPL-2.0-or-later AND CC-BY-3.0
- ubuntu resolute: pcp 7.1.1-1
- ubuntu stonking: pcp 7.2.1-2build1
- Copyright (c) 2014,2019 Red Hat
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms