

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 5
click for more info
Not enough gems
Cost: 6 gems
1: Open a Terminal
incomplete
2: Installing Windows Subsystem for Linux
incomplete
3: Terminal Alternatives
incomplete
4: Download Worldbanc
incomplete
5: Shell Configuration
incomplete
6: PATH Config
incomplete
7: Shell Aliases
incomplete
8: Man
incomplete
9: Symbolic Links
incomplete
10: Top
incomplete
11: Interrupt
incomplete
12: Kill
incomplete
Back
ctrl+,
Next
ctrl+.
This lesson's interactive features are locked, please to keep using them
Sometimes a program is in such a bad state (or is so malicious) that it doesn't respond to the SIGINT, in which case the best option is to use another shell session (new terminal window) to manually kill the program.
kill <PID>
PID stands for "process ID." Every process that's running on your machine has a unique ID. The ps, "process status" command can be used to list the processes running on your machine, and their IDs:
ps aux
The "aux" options just mean "show all processes, including those owned by other users, and show extra information about each process."
You did some digging and found out that the malicious program actually has another mode: force.
./malicious.sh force
Don't include terminal control text like ^C.
You will probably get 2 results: one for the malicious program, and one for the grep command itself. Make sure you use the correct PID, and that you don't miss any characters. You don't want to accidentally kill a system-critical process.
kill <PID>
Run ps aux | head -n 1 to see the header row of the ps aux table.