diff options
author | van Hauser <vh@thc.org> | 2020-08-31 16:34:57 +0200 |
---|---|---|
committer | van Hauser <vh@thc.org> | 2020-08-31 16:34:57 +0200 |
commit | 58cf030546b1fb2dbe9d5325c4e69c0611c4c35b (patch) | |
tree | 2446920ca11be21bef9ed073a614725b1a079255 /docs/parallel_fuzzing.md | |
parent | 18ea9a84476fec095abd88457b635fcaf7f1bb74 (diff) | |
download | afl++-58cf030546b1fb2dbe9d5325c4e69c0611c4c35b.tar.gz |
fix for MacOS sudo
Diffstat (limited to 'docs/parallel_fuzzing.md')
-rw-r--r-- | docs/parallel_fuzzing.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/parallel_fuzzing.md b/docs/parallel_fuzzing.md index 0c4cd237..12895ac3 100644 --- a/docs/parallel_fuzzing.md +++ b/docs/parallel_fuzzing.md @@ -195,7 +195,7 @@ to keep in mind: - Syncing is only necessary for the main nodes on a system. It is possible to run main-less with only secondaries. However then you need to find out which secondary took over the temporary role to be the main node. Look for - the `is_main` file in the fuzzer directories, eg. `sync-dir/hostname-*/is_main` + the `is_main_node` file in the fuzzer directories, eg. `sync-dir/hostname-*/is_main_node` It is *not* advisable to skip the synchronization script and run the fuzzers directly on a network filesystem; unexpected latency and unkillable processes |