Somebody looked at ps, renice, and kill and decided the obvious missing feature was a shotgun.
Visit the psDooM screenshots page
psDooM is a Unix process monitor built on Doom. Running processes appear inside the game as monsters labeled with a process ID and part of the process name.
The joke goes considerably further than a visual skin.
The program periodically checks the machine’s process table and spawns or removes monsters as processes appear and disappear. Damage to a process-monster corresponds to changing that process’s priority with renice. Killing the monster can kill the associated Unix process.
This is therefore one of those rare pieces of software where “shooting the runaway process” can be technically accurate documentation.
The project grew from the release of Doom’s source code in the late 1990s. The psDooM site traces its lineage through XDoom and a University of New Mexico proof of concept called “Doom as a tool for system administration.”
A GUI nobody asked for
A conventional process monitor turns machine state into rows, numbers, percentages, and sortable columns.
psDooM turns the same abstraction into physical space.
Processes occupy a level. They can be approached. Their labels float in front of them. Administrative actions become game actions. The metaphor is ridiculous, but it is also understandable almost immediately to anyone who has played Doom.
That is what makes the project more interesting than a one-line programming gag.
Interface design is largely the business of choosing metaphors for invisible state. Desktop systems use files and folders. Network tools use graphs. psDooM uses demons.
The screenshots page preserves the proof that this really existed, while the main project documentation explains the process-monitoring behavior, supported Doom versions, custom levels, user filtering, and other details.
It is also a snapshot of a specific open-source moment. Once id Software released Doom’s source, programmers did not merely preserve the game. They treated it as reusable infrastructure and started asking increasingly strange questions about what else its engine could represent.
CacheRat’s 1,967 Ancient Web Domains research list includes artifacts like this because software history gets much more interesting when you keep the experiments that were never supposed to become products.
Modern process managers are cleaner, safer, and more useful.
None of them let you circle-strafe Apache.