The solution to that problem is simple. Map the Doom process to doomguy. If you die, the process ends! :) You could even add a bit of code that sends a message to the head sysadmin so if a newbie keeps attacking a big nasty and dying as a result, the sysadmin would know to step over and tell the newbie to chill out.

This also raises an existential conundrum. If the sysadmin has god mode, what happens if they shoot init with a BFG? Kidding of course, but it is fun to imagine an invincible process stepping heroically through the ensuing wreckage of a kernel panic :D

> Certain processes are vital to the computer's operation and should not be killed. For example, after I took the screenshot of myself being attacked by csh, csh was shot by friendly fire from behind, possibly by tcsh or xv, and my session was abruptly terminated.

I installed this at work once. Processes were spawned via a popen() calling ps with some flags. It was easy enough to modify it to grep out the more important processes.