Ever opened a Linux server and thought:
“Why is everything so slow or frozen?”
Most of the time, the problem is not Linux itself.
It’s running processes consuming resources in the background.
Let’s understand it simply.
What is a Process?
A process is a running program or service on your Linux system.
Examples:
- Web browser
- Web server (Nginx/Apache)
- Database (MySQL, PostgreSQL)
- Background services
What is PID?
Every process has a unique ID called a PID (Process ID).
PID = identity number of a running program
Example:
Chrome → PID 1234
Nginx → PID 5678
👉 You use PID to control processes (stop, monitor, debug).
1. Viewing Processes with ps
ps
Shows processes in current terminal only.
Better command:
ps aux
Shows ALL processes with:
CPU usage
Memory usage
User
PID
Command
👉 This is a daily DevOps debugging command.
Full system view:
ps -ef
Shows process hierarchy (parent → child relationships)
Difference:
Command Use
ps aux Resource monitoring (CPU/MEM)
ps -ef Process structure view
2. Real-Time Monitoring top
top
top Shows live system activity:
You can see:
- CPU usage
- Memory usage
- Running processes
Useful keys inside top:
q→ Quit
k→ Kill a process
M→ Sort by memory usage
P→ Sort by CPU usage
👉 Used when servers suddenly slow down or spike.
3. Better version: htop
# Install if not available:
sudo apt install htop # Ubuntu/Debian
sudo dnf install htop # Fedora/RHEL
Why devs prefer htop:
- Colorful UI
- Easier navigation
- Process tree view
- Simple killing of processes
👉 Much more user-friendly than top
4. Finding Specific Processes
ps aux | grep nginx
ps aux | grep python
Better alternatives:
pgrep nginx # Returns only PIDs
pidof nginx # Another way to get PID
👉 Faster way to get PID directly
5. Killing Processes
kill 1234 # Graceful kill
kill -9 1234 # Force kill (use only when necessary)
-> You must know the PID of the process to use kill.
Safer & easier ways:
pkill nginx # Kill by process name
killall firefox # Kill all processes with that name
⚠️ Always double-check PID before killing a process.
Wrong kill = system instability.
6. Background & Foreground Jobs
Foreground Process:
- Runs in terminal and blocks it.
Background Process:
- Runs without blocking terminal
Example:
sleep 100 &
- & → sends process to background
- You can continue using terminal
Useful commands:
jobs → Show background jobs
fg → Bring job to foreground
bg → Resume paused job in background
Useful when multitasking in terminal sessions.
7. Find Heavy Processes (CPU / Memory)
# Sort by CPU (highest first)
ps aux --sort=-%cpu | head
# Sort by Memory (highest first)
ps aux --sort=-%mem | head
👉 Very useful in production debugging.
⚠️ Important Safety Warning
Never kill critical system processes such as:
systemdinit
kernelprocesses (usually shown with square brackets)
👉 Doing so can crash your system completely.
Simple Mental Model
Think of Linux like a city:
- Each app = a citizen
- PID = ID card
- CPU = energy usage
- RAM = working space
Process management = controlling city traffic 🚦
Summary
In this guide you learned:
- What a process is
- What PID means
- How programs run in Linux
- Viewing processes (ps, top, htop)
- Finding processes (grep, pgrep, pidof)
- Killing processes safely (kill, pkill, killall)
- Foreground vs background processes
- Monitoring CPU and memory usage
why This Matters
Process management is used in:
DevOps debugging
Server monitoring
Performance optimization
Cloud environments
Production troubleshooting
👉 This is a core real-world Linux skill.
Next Post:
Linux Disk Usage Explained Simply, (df, du, mounting basics)
Question for You
Have you ever faced a server slowdown because of a single process?
I’ll show how to identify it instantly in Part 6.
SOCIAL SHARE CARD GENERATOR