summaryrefslogtreecommitdiffstats
path: root/wiki/src/contribute/release_process/test/erase_memory_on_shutdown.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'wiki/src/contribute/release_process/test/erase_memory_on_shutdown.mdwn')
-rw-r--r--wiki/src/contribute/release_process/test/erase_memory_on_shutdown.mdwn8
1 files changed, 4 insertions, 4 deletions
diff --git a/wiki/src/contribute/release_process/test/erase_memory_on_shutdown.mdwn b/wiki/src/contribute/release_process/test/erase_memory_on_shutdown.mdwn
index b9cee87..616ee1d 100644
--- a/wiki/src/contribute/release_process/test/erase_memory_on_shutdown.mdwn
+++ b/wiki/src/contribute/release_process/test/erase_memory_on_shutdown.mdwn
@@ -24,7 +24,7 @@ Pick one of those:
address space of a given process is usually limited at 3 GiB - or
less, depends on the kernel configuration); as root:
- for i in $(seq 0 31) ; do fillram & done ; watch -n 1 free -m
+ for i in $(seq 0 31) ; do fillram & done ; watch -n 1 free -m
* The `free` output should allow you to reboot late enough (so that
enough memory is filled) and soon enough (so that the system is
@@ -37,11 +37,11 @@ Pick one of those:
better be careful not rebooting your host system and proceed like
this:
- echo 1 > /proc/sys/kernel/sysrq ; echo b > /proc/sysrq-trigger
+ echo 1 > /proc/sys/kernel/sysrq ; echo b > /proc/sysrq-trigger
* Dump memory and try to find the known pattern in it, e.g.:
- grep -c wipe_didnt_work tails.dump
+ grep -c wipe_didnt_work tails.dump
- you should get some integer larger than zero if the pattern was found in
RAM, which is the expected result;
@@ -60,7 +60,7 @@ Pick one of those:
Tails stick.
* Dump memory and try to find the known pattern in it, e.g.:
- grep -c wipe_didnt_work tails.dump
+ grep -c wipe_didnt_work tails.dump
- you should get zero if the pattern was not found in RAM, which is the
optimal (and expected) result;