It's surprisingly easy to stumble into crash bugs when playing around with processes. I remember a decade or two ago I ran into a linux bug where the kernel wo

It's surprisingly easy to stumble into crash bugs when playing around with processes. I remember a decade or two ago I ran into a linux bug where the kernel would panic if a process was killed with an open descriptor on its /proc entries. That is: open /proc/$pid/something; kill -9 $pid #kernel crash We unfortunately discovered this when using fuser in a runscript to kill stale versions of a process, eg: sudo fuser --kill --namespace tcp 80 # kill whatever is listening on port 80 This would reliably cause kernel panics every so often, with one straightforward shell command. This ended up causing a big problem because it was part of a runscript which ran on bootup. But, it normally would do nothing so it went unnoticed until the app in question had a startup problem, leaving a copy of itself dangling listening on the port -- and instead of killing the old instance, it began crashing the entire system in a loop. Oops.