aboutsummaryrefslogtreecommitdiff
path: root/README.md
blob: 527d63cc6dd72956cd62b955843f684ed858a909 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
doomsh
======

Use `ulimit` to severely restrict your Bash shell's resources, and see how long
you can last before segfaulting or giving up.

The author highly recommends you create a dummy user to run this, so that you
don't end up munging important files in your `HOME`.

    $ sudo useradd -m doomguy
    $ sudo -i -u doomguy
    $ git clone https://dev.sanctum.geek.nz/code/doomsh.git
    $ cd doomsh
    $ ./doomsh

Not really important or useful in any way, but kind of fun to see what breaks
when resources are really tight, especially when it exposes problems in
programs like failing to check for NULL returns from `malloc(3)`.

On the author's machine, at level 5, even `ls(1)` doesn't work, let alone Vim.

If you're really crazy, you'll try and launch X11 processes from it, and watch
them twitch as they die.

READ THE LICENSE. THE AUTHOR WAIVES ALL RESPONSIBILITY FOR ANYTHING THIS DOES
TO YOUR COMPUTER, YOUR DATA, OR YOUR DOG.

License
-------

Copyright (c) [Tom Ryder][1]. Distributed under an [MIT License][2].

[1]: https://sanctum.geek.nz/
[2]: https://www.opensource.org/licenses/MIT