X-Git-Url: https://git.exim.org/buildfarm-client-wiki.git/blobdiff_plain/c780e4883bfc8da405a481518a5abef363a412eb..9ba472b344b17e52d5bbf98913ac23b9c86abe6f:/Installation.md

diff --git a/Installation.md b/Installation.md
index c909dad..4fc1b3c 100644
--- a/Installation.md
+++ b/Installation.md
@@ -23,7 +23,7 @@ This will create the repo checkout in the directory *~/code/*.
 10. Whatever directory is set as the *build_root* must exist before anything will run.  If you didn't change it, this will be all that's needed:
 `mkdir $HOME/buildfarm`
 11. Directory permissions must be lax enough for the **exim** user running the test suite to be able to access the files that user farm has checked out.  One recommendation that we know works is to make the **farm** user's home directory be both group and world readable and group and world searchable:
-`chmod og+rx $HOME`.  Additionally, every subdirectory between */* and *$HOME/buildfarm* should have this permissive access.
+`chmod og+rx $HOME`.  Additionally, every subdirectory between */* and *$HOME/buildfarm* should have this permissive access.  One thing that these tighter permissions will break, for example, is test 0005, because the sudo'd exim process in the test suite will be unable to read that test config file.
 12. Make sure that your umask is 0022: `umask 0022`.  This also will need to be set in any script you call the run_build.pl script.
 13. Test the configure process by running `./run_build.pl --test --verbose=2 --only-steps=configure`. If there are errors, you'll need to correct them until the process succeeds (ends with OK).  You can repeat this as many times as necessary because test mode does not store the status of the git repo or the status of each stage of the build.
 14. Test the build process by running `./run_build.pl --test --verbose=2 --only-steps=configure,make`. If there are build errors, make adjustments, install additional packages, etc, and repeat the test.