aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Ryder <tom@sanctum.geek.nz>2016-07-18 21:39:48 +1200
committerTom Ryder <tom@sanctum.geek.nz>2016-07-18 21:40:55 +1200
commitbc9005e441d87b5dd0c056a68191bf86c3e3790b (patch)
tree1dc83432954607ea8af3462758d61992a5e1ede9
parentTidying up license files (diff)
downloaddoomsh-bc9005e441d87b5dd0c056a68191bf86c3e3790b.tar.gz
doomsh-bc9005e441d87b5dd0c056a68191bf86c3e3790b.zip
Recommend a dummy userv0.1.0
-rw-r--r--README.markdown9
1 files changed, 9 insertions, 0 deletions
diff --git a/README.markdown b/README.markdown
index 7055bee..0205678 100644
--- a/README.markdown
+++ b/README.markdown
@@ -4,6 +4,15 @@ 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://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)`.