Process & Resource Monitoring (Top/Htop/Ps/Systemd)

Stop pstree from making you squint at your process tree

🧩 The Challenge

Trying to hunt down which child process is eating memory in a deeply nested application stack usually results in a messy wall of text that makes your eyes glaze over. We’ve all spent way too long trying to trace parent-child relationships in a standard ps output while a server is actively melting down.

💡 The Fix

Use pstree with a few specific flags to visualize the process hierarchy as a clean, structured map rather than a flat, confusing list. It saves you from having to mentally map out who started what when everything is crashing.

pstree -aps $(pgrep -f [process_name])

⚙️ Why It Works

Adding the -a flag includes the command line arguments so you can distinguish between similar workers, while -p shows the PIDs and -s limits the tree to the specific process you’re chasing. It turns a chaotic process list into a logical map that actually makes sense when you’re under pressure.

🚀 Pro-Tip: Pipe it into less if you’re dealing with a Java app or something else that spawns a thousand sub-processes.

Linux Tips & Tricks | © ngelinux.com | 7/31/2026