From c780e4883bfc8da405a481518a5abef363a412eb Mon Sep 17 00:00:00 2001 From: Todd Lyons Date: Fri, 30 May 2014 17:28:59 -0700 Subject: [PATCH 1/1] Additional path permissions recommendation --- Installation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Installation.md b/Installation.md index aea4168..c909dad 100644 --- a/Installation.md +++ b/Installation.md @@ -22,8 +22,8 @@ This will create the repo checkout in the directory *~/code/*. 9. Edit the *build-farm.conf* file and adjust to your local configuration. The only options that absolutely require changing are the _animal_ and _secret_ configuration settings. Your machine's sysname alias must be assigned to *animal* and the secret key assigned to *secret*. The rest of the default build configuration should work to build a basic Exim configuration with no added features/capabilities and it will run the test suite. 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. Make the **farm** user's home directory be world readable and world searchable: -`chmod o+rx $HOME` +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. 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. -- 2.30.2