summaryrefslogtreecommitdiffstats
path: root/system/memtester/README
diff options
context:
space:
mode:
author B. Watson <yalhcru@gmail.com>2020-06-06 09:12:44 +0700
committer Willy Sudiarto Raharjo <willysr@slackbuilds.org>2020-06-06 09:12:44 +0700
commitd1fb1dbca9b4a400899d2d96d2cbd5a1821da20a (patch)
tree88ba879ff83241655be93f78b58120c314068816 /system/memtester/README
parent017233c05e7e0f60476156f12c5572db2c3df5b5 (diff)
downloadslackbuilds-d1fb1dbca9b4a400899d2d96d2cbd5a1821da20a.tar.gz
slackbuilds-d1fb1dbca9b4a400899d2d96d2cbd5a1821da20a.tar.xz
system/memtester: Added (memory test utility).
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'system/memtester/README')
-rw-r--r--system/memtester/README23
1 files changed, 23 insertions, 0 deletions
diff --git a/system/memtester/README b/system/memtester/README
new file mode 100644
index 0000000000..df134f1b2e
--- /dev/null
+++ b/system/memtester/README
@@ -0,0 +1,23 @@
+memtester (memory test utility)
+
+memtester is a userspace utility for testing the memory subsystem for
+faults. Unlike memtest86, it runs as a process on a running Linux system,
+meaning it can't test all of memory the way memtest86 is able to... but
+you don't have to reboot to use it.
+
+Note that, by definition, memtester counts as a denial-of-service
+(resource exhaustion) attack against the local machine. Be cautious
+about using it, and definitely *read its man page* before use.
+
+memtester has traditionally been run as root, so that it can lock the
+memory it's testing to prevent swapping and remapping. However, it's
+possible to use capabilities to allow it to run correctly as a normal
+user. Use something like:
+
+# chown root:console /usr/bin/memtester
+# chmod 0750 /usr/bin/memtester
+# setcap cap_ipc_lock=ep /usr/bin/memtester
+
+This allows anyone in the "console" group to run memtester. You could
+also create a memtester group and use it in the chown command above,
+if you'd rather have more fine-grained control.