From 3a258ad5cdd98c5705af6c02ba91993b3d382adc Mon Sep 17 00:00:00 2001 From: Barry Warsaw Date: Wed, 5 Dec 2007 17:23:41 -0500 Subject: Because the admin directory is no longer included, the www directory isn't either, and that's where the generated docs used to live. So now, make this directory include the generated docs, removing the old IPC7 and LISA-98 directories, and the .tex source files. These latter are moved to the admin repository. --- doc/mailman-install/node9.html | 147 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 147 insertions(+) create mode 100644 doc/mailman-install/node9.html (limited to 'doc/mailman-install/node9.html') diff --git a/doc/mailman-install/node9.html b/doc/mailman-install/node9.html new file mode 100644 index 00000000..e08e4f38 --- /dev/null +++ b/doc/mailman-install/node9.html @@ -0,0 +1,147 @@ + + + + + + + + + + + + + +4 Check your installation + + + + + +

+4 Check your installation +

+ +

+After you've run make install, you should check that your +installation has all the correct permissions and group ownerships by running +the check_perms script. First change to the installation +(i.e. $prefix) directory, then run the bin/check_perms +program. Don't try to run bin/check_perms from the source directory; it will +only run from the installation directory. + +

+If this reports no problems, then it's very likely <wink> that your +installation is set up correctly. If it reports problems, then you can either +fix them manually, re-run the installation, or use bin/check_perms +to fix the problems (probably the easiest solution): + +

+ +

You need to become the user that did the installation, and that owns all + the files in $prefix, or root. + +
+
Run bin/check_perms -f + +
+
Repeat previous step until no more errors are reported! +

+ +

Warning: + +If you're running Mailman on a shared multiuser system, and you have mailing +lists with private archives, you may want to hide the private archive +directory from other users on your system. In that case, you should drop the +other execute permission (o-x) from the archives/private directory. +However, the web server process must be able to follow the symbolic link in +public directory, otherwise your public Pipermail archives will not work. To +set this up, become root and run the following commands: + +

+# cd <prefix>/archives
+# chown <web-server-user> private
+# chmod o-x private
+

+ +

+You need to know what user your web server runs as. It may be www, +apache, httpd or nobody, depending on your server's +configuration. +

+ +

+ + + + -- cgit v1.2.3