Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml,v
diff -u -r1.18 -r1.19
--- openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml 4 Feb 2004 16:47:35 -0000 1.18
+++ openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml 12 Feb 2004 13:51:43 -0000 1.19
@@ -112,7 +112,8 @@
[service0 service0]$ cd /var/lib/aolserver
[service0 aolserver]$ tar xzf /tmp/&tarballpath;.tgz
[service0 aolserver]$ mv &tarballpath; service0
-[service0 aolserver]$ chmod -R 700 service0
+[service0 aolserver]$ chmod -R 775 service0
+[service0 aolserver]$ chown -R service0.service0 service0
[service0 aolserver]$ ls -al
total 3
drwxrwx--- 3 root web 1024 Mar 29 16:41 .
@@ -125,7 +126,8 @@
cd /var/lib/aolserver
tar xzf /tmp/&tarballpath;.tgz
mv &tarballpath; service0
-chmod -R 700 service0/
+chmod -R 755 service0
+chgrp -R service0.service0 service0
exit
@@ -333,8 +335,8 @@
Vacuuming
[service0 service0]$ export EDITOR=emacs;crontab -e
- Add this line to the file. The numbers and stars at the beginning are cron columns that specify when the program should be run - in this case, whenever the minute is 0 and the hour is 1, i.e., 1:00 am every day.
- 0 1-23 * * * /usr/local/pgsql/bin/vacuumdb --full --analyze service0
+ Add these lines to the file. The vacuum command cleans up temporary structures within a PostGreSQL database, and can improve performance. We vacuum gently every hour and completely every day. The numbers and stars at the beginning are cron columns that specify when the program should be run - in this case, whenever the minute is 0 and the hour is 1, i.e., 1:00 am every day, and every (*) day of month, month, and day of week. Type man 5 crontab for more information.
+ 0 1-23 * * * /usr/local/pgsql/bin/vacuumdb --analyze service0
0 0 * * * /usr/local/pgsql/bin/vacuumdb --full --analyze service0
@@ -442,21 +444,18 @@
Kill any current running AOLserver processes and start a new
- one. If you are using Oracle, rather than PostgreSQL, replace
- nsd-postgres with
- nsd-oracle).
- If you want to use port 80, there are complications.
- First, AOLserver must be root to use system ports such as
- 80, but refuses to run as root for security reasons. Thus
- you must start as root and specify a non-root user ID and
+ one. The recommended way to start an AOLserver process is by running the included script, /var/lib/aolserver/service0/packages/etc/daemontools/run. If you are not using the default file paths and names, you will need to edit run.
+ If you want to use port 80, there are complications. AOLserver must be root to use system ports such as
+ 80, but refuses to run as root for security reasons. So, we call the run script as root and specify a non-root user ID and
Group ID which AOLserver will switch to after claiming the
port. To do so, find the UID and GID of the
service0 user via
grep service0
/etc/passwd and then put those numbers into
the command line via -u
501 -g
- 502. Second, if you are root then killall will affect all OpenACS services on the machine, so if there's more than one you'll have to do ps -auxw | grep
+ 502. In AOLserver 4, you must also send a -b flag. Do this by editing the run file as indicated in the comments.
+ If you are root then killall will affect all OpenACS services on the machine, so if there's more than one you'll have to do ps -auxw | grep
nsd and selectively kill by job number.
[service0 etc]$ killall nsd
nsd: no process killed
@@ -617,7 +616,7 @@
Set up database environment variables for the site
- user. These settings are necessary for working with the
+ user. Depending on how you installed Oracle or PostGreSQL, these settings may be necessary for working with the
database while logged in as the service user. They do not
directly affect the service's run-time connection with the
database, because those environmental variables are set by the