Add required argument to run_cron.sh

diff --git a/Installation.md b/Installation.md
index 01bbfd9071d4e117d9da5281af84f8298a06cfbc..9dd6eebd77ef1824e0a3294b438ea0bd4e4a1e48 100644 (file)
--- a/Installation.md
+++ b/Installation.md
@@ -24,7 +24,7 @@ This will create the repo checkout in the directory *~/code/*.
 14. Test the test suite by running `./run_build.pl --test --verbose=2 --only-steps=configure,make,test --override range_num_tests='1 2'`.  If there are build errors when building the test suite, or runtime errors trying to run the test suite, you may need to install additional packages (you shouldn't though).
 15. If you enabled the documentation building process in the *build-farm.conf*, then you can try to build it with `./run_build.pl --test --verbose=2 --only-steps=configure,build_docs`.  For documentation generation to succeed, it will require extra packages to be installed to support xml, xslt, pdf, and a few other things.
 16. If you can get past each of these steps, then your build farm system meets the minimum requirements.
-17. The official process can be kicked off by running `/home/farm/code/run_cron.sh`.  This will run the default build configuration, keep track of the git repository status, and upload the build results to the server.
+17. The official process can be kicked off by running `/home/farm/code/run_cron.sh --run-all`.  This will run the default build configuration, keep track of the git repository status, and upload the build results to the server.
 18. Once that command runs with no complaints, add it to the **farm** user crontab.  You can run it at whatever frequency you choose, I suggest 1 hour.  If a previous instantiation is still running, the script will detect the lockfile and exit so as not to step on each other.
 
 ## Overview