diff options
author | hexcoder- <heiko@hexco.de> | 2020-08-31 14:47:22 +0200 |
---|---|---|
committer | hexcoder- <heiko@hexco.de> | 2020-08-31 14:47:22 +0200 |
commit | 7fb72f10387979ac5e46fdfb8901e928901a94e7 (patch) | |
tree | 34d52adc8cdc3c3f13fa51a2fcb499d82c1653a9 /docs/parallel_fuzzing.md | |
parent | d2c9e4baa74210cf49243390fb3dabb29024ade4 (diff) | |
download | afl++-7fb72f10387979ac5e46fdfb8901e928901a94e7.tar.gz |
typos
Diffstat (limited to 'docs/parallel_fuzzing.md')
-rw-r--r-- | docs/parallel_fuzzing.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/parallel_fuzzing.md b/docs/parallel_fuzzing.md index 14c237c1..0c4cd237 100644 --- a/docs/parallel_fuzzing.md +++ b/docs/parallel_fuzzing.md @@ -206,9 +206,9 @@ in I/O wait state can mess things up. You can use screen, nohup, tmux, or something equivalent to run remote instances of afl-fuzz. If you redirect the program's output to a file, it will automatically switch from a fancy UI to more limited status reports. There is -also basic machine-readable information always written to the fuzzer_stats file -in the output directory. Locally, that information can be interpreted with -afl-whatsup. +also basic machine-readable information which is always written to the +fuzzer_stats file in the output directory. Locally, that information can be +interpreted with afl-whatsup. In principle, you can use the status screen of the main (-M) instance to monitor the overall fuzzing progress and decide when to stop. In this |