- Why is it worth finding the exact PID before stopping a process?
- What should you inspect before deciding to terminate something from the CLI?
M20 - Process Management: CLI
List, filter, and stop processes from the command line with a stronger habit of inspecting before terminating.
Processes
Process Management: CLI
List, filter, and stop processes from the command line with a stronger habit of inspecting before terminating.
40 min INTERMEDIATE BOTH Field-verified
Before this lesson
What you should learn
- List, filter, and stop processes from the command line with a stronger habit of inspecting before terminating.
Visual model
Concept to practice path
Each lesson is meant to move from an idea, to an example, to a safe practice step.
Open the full visualWhy This Matters
The CLI becomes essential when:
- you are on a remote system with no GUI
- many similar processes are running
- you need a precise command you can repeat
But precision matters. The wrong kill command pointed at the wrong PID can stop the wrong work.
Safety sequence
CLI process safety order
- List processes before you act.
- Filter to the exact target and confirm the name or PID.
- Use a normal stop first when possible.
- Verify that only the intended process changed state.
1. List Processes
Start by seeing what is running.
Get-Process
ps aux
This gives you the big picture, but usually too much detail for one task.
2. Narrow the Target
The next step is to filter down to the process you actually care about.
Get-Process | Where-Object { $_.ProcessName -like 'code' }
Get-Process -Name notepad
ps aux | grep ssh
ps -ef | grep python
The goal is to confirm identity first, not to jump straight to termination.
3. Stop Only When You Mean It
Once you are confident about the target, you can stop it.
Stop-Process -Id 1234
or by name when appropriate
Stop-Process -Name notepad
kill 1234
stronger signal only if the normal one does not work
kill -9 1234
Escalation Rule
Use gentler termination first when possible. Reserve stronger force for cases where inspection tells you the process is truly stuck and a normal stop is not working.
A Better Process Habit
Use this sequence:
- list processes
- narrow the target
- verify name or PID
- stop only if needed
- confirm the result afterward
That sequence is more important than memorizing lots of commands.
What to Ignore for Now
- signals beyond the basic idea
- per-thread process debugging
- daemon supervision internals
The important thing is learning precise inspection and cautious control.
Before You Move On
You are ready when you can:
- list processes on your platform
- narrow down to a target process
- explain why finding the exact PID reduces mistakes
Next, we look at foreground and background jobs so process control feels even more practical.
Learning loop
Recall it, check it, then practice it.
Do this before moving on. It turns reading into memory and safer action.
- List processes and isolate one target process without notes.
- Explain the difference between inspecting a process and stopping it.
Review again after 1, 2, 5 days.
What to do next
Best next step PracticeUse the matching lab or keep building skill in practice.