Fork 0
Variety of misbehaving processes.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Simon de Vlieger 39eef39932
pylons: meme
9 months ago
src pylons: meme 9 months ago
.gitignore Initial. 3 years ago
LICENSE Update license. 3 years ago
Makefile Initial. 3 years ago
README.md danger: enable building of DANGER progs 9 months ago


Ministry of Silly Processes

A collection of processes that misbehave, act weirdly, or are just plain unnecessary. For use in testing or just to see if your system administration skills are up to par.

Of special note, the processes in this repository are split into two parts. The first set of processes are relatively benign. They do not access any non-transient resources and do not leave anything after their execution completes.

The second set of processes are harmful to your system. They will try to make your system break down in non-permanent ways. If you run these processes there is a good chance that your machine will stop responding so do not take these these lightly.


Clone this repository and run make to create the executables for your system. This will build the standard set of safe processes for usage. If you want to also create binaries for the dangerous set of processes then run make i-dont-need-warranty.


After compiling the processes they end up in the bin/ directory. You can them with ./bin/mosp-friendly.

To use the dangerous set of processes you will additionally need to confirm that you really want to to do this by providing an enviornment variable in the following way VOIDMYWARRANTY=1 ./bin/mosp-DANGER-pylons, these processes will not start if the environment variable is not set.

Introducing the processes

These processes are included with the Ministry of Silly Processes.


Exits immediately with exit code 0.


Exits immediately with exit code 1.


Sleeps forever then exits with code 0.


Writes garbage on stdout, stderr, forever then exits with code 0.


Doesn't listen to any signals, sleeps forever, then exits with code 0.


Immediately segfaults.


Tries to consume all shared resources on the system, enters a busy loop, ignores all signals, and then exits with code 0.