Index: openacs-4/packages/acs-core-docs/www/install-openacs-keepalive.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-openacs-keepalive.html,v diff -u -r1.24 -r1.25 --- openacs-4/packages/acs-core-docs/www/install-openacs-keepalive.html 27 Oct 2014 16:39:21 -0000 1.24 +++ openacs-4/packages/acs-core-docs/www/install-openacs-keepalive.html 7 Aug 2017 23:47:50 -0000 1.25 @@ -1,5 +1,5 @@ -
The simplest way to start and stop and OpenACS site is to run the startup shell script provided, /var/lib/aolserver/$OPENACS_SERVICE_NAME/etc/daemontools/run
. This runs as a regular task, and logs to the logfile. To stop the site, kill the script.
A more stable way to run OpenACS is with a "keepalive" mechanism of some sort, so that whenever the server halts or is stopped for a reset, it restarts automatically. This is recommended for development and production servers.
The Reference Platform uses Daemontools to control AOLserver. A simpler method, using init
, is here.
Daemontools must already be installed. If not, install it.
Each service controlled by daemontools must have a +
The simplest way to start and stop and OpenACS site is to run the startup shell script provided, /var/lib/aolserver/$OPENACS_SERVICE_NAME/etc/daemontools/run
. This runs as a regular task, and logs to the logfile. To stop the site, kill the script.
A more stable way to run OpenACS is with a "keepalive" mechanism of some sort, so that whenever the server halts or is stopped for a reset, it restarts automatically. This is recommended for development and production servers.
The Reference Platform uses Daemontools to control AOLserver. A simpler method, using init
, is here.
Daemontools must already be installed. If not, install it.
Each service controlled by daemontools must have a
directory in /service
. That
directory must have a file called
run
. It works like this:
The init
program starts every
@@ -62,8 +62,8 @@
[root root]#
Verify that the controls work. You may want to tail -f /var/lib/aolserver/$OPENACS_SERVICE_NAME/log/$OPENACS_SERVICE_NAME-error.log
in another window, so you can see what happens when you type these commands.
- Most of this information comes from Tom Jackson's AOLserver+Daemontools - Mini-HOWTO. -
Table 6.1. How it Works
Program | Invoked by this program ... | ... using this file | Where to find errors | Log goes to | Use these commands to control it | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
svscanboot
+ More information can be found on the AOLserver
+ Daemontools page.
+ Table 6.1. How it Works
| /service/$OPENACS_SERVICE_NAME/run | /var/lib/aolserver/$OPENACS_SERVICE_NAME/log/error.log | /var/lib/aolserver/$OPENACS_SERVICE_NAME/log/$OPENACS_SERVICE_NAME.log | svc -k /service/$OPENACS_SERVICE_NAME | ||||||||||||||||||||||||
postgresql | Redhat init scripts during boot | /etc/init.d/postgresql | /usr/local/pgsql/data/server.log | service postgresql start (Red Hat), /etc/init.d/postgresql start (Debian) |