In Level 10 of my Linux Escape Room series, I finally hit double digits, and this one is all about processes—specifically a “locked” (yeah, in quotes) process that’s basically hung and needs to be killed so you can unlock the exit. I start by showing how to pull the correct level from my Docker Hub by swapping the tag to 10, then I walk through the usual intro/help flow so you know what you’re solving for. The room gives you a script that won’t hand over the key until that locked process is gone. From there, I keep it practical: I use ps (and variations like ps -f or ps aux depending on your Linux flavor) to list what’s running, then I grep mentally for anything that looks like “locked.” In this container it’s pretty easy to spot a script that’s sleeping for 24 hours, which is a great example of something that doesn’t need to be hanging around. I grab the PID and use kill to terminate it, then rerun the script to get the key and escape. Biggest takeaway: knowing how to inspect and kill processes is a super useful troubleshooting skill in a homelab—just be way more careful doing this on production systems if you don’t know what a process is doing.