PLIMIT(1)

📦
version 0.2.23 · 2 versions
, in fedora 44

✨ PLIMIT(1) — the process resource limits girlie ✨

okay bestie, welcome to plimit, a manual page from the General Commands Manual section of your fave Unix system. she's giving "let me peek at what your processes are allowed to do" energy and honestly? iconic. 💅

🌸 NAME 🌸

plimit — get process resource limits 🫶

🎀 SYNOPSIS 🎀

plimit [-km] [pid | core]...

💖 DESCRIPTION 💖

so basically, plimit prints the resource limits of each process or process core file you hand it. for every single resource, it shows you two things: the current (soft) limit and the maximum (hard) limit. that's it, that's the whole vibe. no cap. ✨

🦋 OPTIONS 🦋

  • -k — display file and memory sizes in kilobytes instead of in bytes. tiny numbers, big slay. 💅
  • -m — display file and memory sizes in megabytes instead of in bytes. for when you simply cannot deal with that many digits. 😭

🌈 OPERANDS 🌈

  • pid — a Process ID list, bestie. you can also pass a /proc/pid path, which means shell expansions like /proc/* work and you can target all processes on the system in one go. main character energy fr fr. 👑
  • core — a 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's been removed, the corresponding systemd journal entry gets used instead. see NOTES below, iykyk. 🫶

💀 EXIT STATUS 💀

  • 0 on success 🎉
  • non-zero if an error occurs — like no such process, permission denied, or an invalid option. she said nope. 😭

🍓 FILES 🍓

  • /proc/pid/* — process information and control files. the whole little neighborhood of a process. 🏘️

🧚 NOTES 🧚

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, 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. it's giving "ghost file but the receipts remain." 💅

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. so fancy. ✨

🌟 SEE ALSO 🌟

ulimit(1), getrlimit(2), coredumpctl(1), proc(5)

and that's the whole page bestie, you ate. 🎀 this was plimit version 0.2.23, dated September 2026 — go forth and check those limits, periodt. 💖🦋🌸

📦 where this page comes from