PAUXV(1)

✨ PAUXV(1) ✨

okay bestie, welcome to the General Commands Manual section for pauxv 💖 — pull up a chair, we're about to snoop on some processes (consensually, it's literally what the tool is for).

---

🎀 NAME 🎀

pauxv — print process auxiliary vector. that's it, that's the whole job, and she does it flawlessly 💅

---

🦋 SYNOPSIS 🦋

pauxv [pid | core]...

---

🌸 DESCRIPTION 🌸

So here's the vibe: you point pauxv at a target process or a process core file, and it prints that process's auxiliary vector. no cap, that's the entire personality.

lowkey the tea though? this command is equivalent to running pargs(1) with the -x option. same energy, shorter to type. iykyk ✨

---

👑 OPERANDS 👑

• pid — the Process ID list. you can also slide in a /proc/pid path instead, which means shell expansions like /proc/* work and will target every single process on the system 🌈 (go off, wildcard).
• core — a Process core file, as produced by systemd-coredump(8), or an Ubuntu/Debian apport .crash file. and here's the iconic part for systemd core files: the file does not need to exist on disk — if it's been removed, the corresponding systemd journal entry gets used instead 🫶. see NOTES below for the full lore.

---

💀 EXIT STATUS 💀

• 0 — success, we ate 💅
• non-zero — something went wrong, like no such process, permission denied, or an invalid option 😭

---

🍓 FILES 🍓

• /proc/pid/* — Process information and control files. the motherlode 💜

---

🧚 NOTES 🧚

okay so 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 that case you can pass the path to the deleted core file as the core operand even though the file no longer exists on disk, and process metadata will be retrieved from the journal entry instead. not me thinking that's actually so smart.

need the path of a missing core file? use coredumpctl(1), like this:

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. main character file format fr fr ⭐

---

💖 SEE ALSO 💖

pargs(1), penv(1), coredumpctl(1), proc(5) — go read them, they're all part of the friend group 🫶

---

and that's the whole page, bestie!! this was pauxv 0.2.23, dated September 2026, living in the General Commands Manual — slay, stay curious, and go print somebody's auxiliary vector responsibly 💅✨🦋