penv - Man Page

penv [pid | core]...

Examine a target process or process core file and print environment variables and values. For live processes, the environment is read from process memory via the environ symbol and reflects the current state, including any variables added or modified at runtime with setenv(3) or putenv(3). This is in contrast to /proc/pid/environ, which is a static snapshot captured at process start. This command is equivalent to running pargs(1) with the -e option.

pid

Process ID list. A /proc/pid path may also be used, allowing shell expansions like /proc/* to target all processes on the system.

core

Process core file, as produced by systemd-coredump(8), or an Ubuntu/Debian apport .crash file. For systemd core files, the file does not need to exist on disk; if it has been removed, the corresponding systemd journal entry will be used instead. See Notes below.

0 on success, non-zero if an error occurs (such as no such process, permission denied, or invalid option).

/proc/pid/*

Process information and control files.

When a core file has been removed by systemd-tmpfiles(8) or by storage limits configured in coredump.conf(5), the systemd-coredump(8) journal entry for the crash may still be available. In this case, the path to the deleted core file can be passed as the core operand even though the file no longer exists on disk, and process metadata will be retrieved from the journal entry instead. Use coredumpctl(1) to obtain the path of a missing core file, e.g., coredumpctl list <name> -F COREDUMP_FILENAME.

Ubuntu/Debian apport .crash files are also supported. These files use Debian control syntax with base64-encoded gzip core dumps. Text fields (such as ProcCmdline, ProcEnviron, and ExecutablePath) are mapped to COREDUMP_* fields, and the core dump is extracted on first access.

pargs(1), pauxv(1), coredumpctl(1), environ(7), proc(5)

pargs(1), pauxv(1).