The simplest way to start and stop and OpenACS site is to run the startup shell script provided,
/var/lib/aolserver/. 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 must have a file called
run. It works like this:
init program starts every
time the computer is booted.
A line in
/etc/inittab, tells init to
run, and to restart if necessary,
every few seconds.
If it sees a subdirectory there, it
looks for a file in the subdirectory called
run. If it finds a run file, it creates a
supervise executes the run script. Whenever the run script stops,
supervise executes it again. It also creates additional control files in the same directory.
Hence, the AOLserver
instance for your development server is started by the file
But we use a symlink to make it easier to add and remove
stuff from the
the actual location is
Daemontools creates additional files and directories to track status and
log. A daemontools directory is included in the OpenACS tarball at
/var/lib/aolserver/. To use it, first ill any existing AOLserver instances. As root, link the
daemontools directory into the
/service directory. Daemontools'
svscan process checks this directory every five seconds, and will quickly execute
killall nsdnsd: no process killed [$OPENACS_SERVICE_NAME etc]$
emacs /var/lib/aolserver/[$OPENACS_SERVICE_NAME etc]$
ln -s /var/lib/aolserver/
Verify that AOLserver is running.
ps -auxw | grep nsd
$OPENACS_SERVICE_NAME5562 14.4 6.2 22436 15952 ? S 11:55 0:04 /usr/local/aolserver/bin/nsd -it /var/lib/aolserver/
$OPENACS_SERVICE_NAME/etc/config.tcl -u serve root 5582 0.0 0.2 3276 628 pts/0 S 11:55 0:00 grep nsd [root root]#
$OPENACS_SERVICE_NAME can now control the service
$OPENACS_SERVICE_NAME with these commands:
svc -d /service/ -
Bring the server down
svc -u /service/ -
Start the server up and leave it in keepalive mode.
svc -o /service/ -
Start the server up once. Do not restart it if it stops.
svc -t /service/ -
Stop and immediately restart the server.
svc -k /service/ -
Sends the server a KILL signal. This is like KILL -9. AOLserver
exits immediately. If svc -t fails to fully kill AOLserver, use
this option. This does not take the server out of keepalive mode, so it should still bounce back up immediately.
Install a script to automate the stopping and starting
of AOLserver services via daemontools. You can then restart a service via
cp /var/lib/aolserver/[root root]#
chmod 755 /usr/local/bin/restart-aolserver[root root]#
At this point, these commands will work only for the
root user. Grant permission for the
web group to use
svc commands on the
/usr/local/bin/svgroup web /service/[root root]#
Verify that the controls work. You may want to
tail -f /var/lib/aolserver/ in another window, so you can see what happens when you type these commands.
More information can be found on the AOLserver Daemontools page.
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||init||/etc/inittab||ps -auxw | grep readproctitle||n/a|
|aolserver||/service/||/var/lib/aolserver/||/var/lib/aolserver/||svc -k /service/|
|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)|