RUNASPCP(1)
β¨ RUNASPCP(1) β¨
okay bestie, welcome to the General Commands Manual entry for runaspcp π
buckle up, it's giving "tiny tool, big responsibilities".
πΈ NAME πΈ
runaspcp β execute a shell command as the user ``pcp''
π SYNOPSIS π
$PCP_BINADM_DIR/runaspcp [-D debug] [-s shell] command
π DESCRIPTION π
so basically, runaspcp runs the single argument command as the user $PCP_USER and group $PCP_GROUP β and both of those come straight from /etc/pcp.conf. no cap, that's the whole personality. π
By default the command gets run by sh(1), or you can swap in a different shell using the -s (or --shell) command line argument. pick your fighter π¦
Normally runaspcp is used from the PCP init'' scripts that are launched as root'' but need to downgrade their privileges when running some PCP daemons as the ``pcp'' user. literally the "start as the boss, clock out into a normal human" arc π iconic behaviour, lowkey essential.
The -?, --help option displays a usage message. always here to help fr fr π«Ά
π₯ DIAGNOSTICS π₯
The exit status is 1 if runaspcp cannot change user or group, or cannot execute the shell, else the exit status of command.
so if it fails at the privilege-swap step or the shell won't launch, you get a 1. otherwise you inherit whatever command decided to return. vibes passed through, respectfully. π
π 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. The $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf(5). β¨
π§ DEBUGGING OPTIONS π§
The -D or --debug option enables the output of additional diagnostics on stderr to help triage problems, although the information is sometimes cryptic and primarily intended to provide guidance for developers rather than for end-users. ngl it's giving "devs only, bestie, you're not ready for this lore" π
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 runaspcp are as follows:
appl0β verbose diagnostics π£οΈ
friendly reminder from your girl: the debugging output is cryptic on purpose-ish and aimed at developers, not end-users. don't come for me when it looks like alphabet soup. π
and that's the page, bestie!! this was brought to you by Performance Co-Pilot, living under the PCP umbrella, in the RUNASPCP(1) era β periodt. π β¨ go run your commands safely, downgrade those privileges, and slay. ππ
π¦ 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
- 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.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 stonking: pcp 7.2.1-2build1
- Copyright (c) 2024 Ken McDonell. All Rights Reserved
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms