Processes and Jobs for DevOps Engineers
Processes and jobs describe how Linux runs programs. Each running program is a process with a PID, parent, state and resource use, inspected with ps, top and htop. Signals such as SIGTERM and SIGKILL control them, while foreground and background jobs, nice values and tools like nohup and tmux manage long tasks.
Stage: Linux · Part of the DevOps Engineer roadmap · Last reviewed 19 November 2026
What to learn in Processes and Jobs
- List and filter processes with ps and top
- Stop processes with kill, using the right signal
- Run tasks in the background and bring them back with jobs, bg and fg
- Keep a job alive after logout using nohup or tmux
- Change priority with nice and renice
- Explain zombie and orphan processes
Processes and Jobs interview questions
What is the difference between SIGTERM and SIGKILL?
SIGTERM asks a process to terminate and can be caught, so the program can clean up. SIGKILL cannot be caught or ignored and ends the process immediately without cleanup. Try SIGTERM first and use SIGKILL only when a process will not stop.
What is a zombie process?
A zombie has finished running but still has an entry in the process table because its parent has not yet read its exit status. It uses no CPU or memory beyond the entry. Fix it by making the parent reap it, or ending the parent.
Where Processes and Jobs fits in the DevOps Engineer roadmap
Processes and Jobs belongs to the Linux stage (beginner level). Operating system fundamentals: the Linux course.
Other units in this stage
- Start Here (free)
- Navigating the Filesystem
- Working with Files
- Text Editors
- Users, Groups and Permissions
- Text Processing and Pipes
- Package Management
- The Shell Environment
- Bash Scripting
- Archives, Storage and Filesystems
- Networking and SSH
- Services, Boot and Logs
- Security Basics
- Real Server Admin
- Linux for DevOps
- Capstones and Placement Prep
Back to the full DevOps Engineer roadmap