| Prev | Chapter 15. Kernel Documentation | Next |
|---|
Tcl code: /tcl/0-acs-init.tcl and /packages/acs-kernel/bootstrap.tcl
This document describes the startup (bootstrapping) process for an AOLserver +
By Jon Salz
+</authorblurb> + +Tcl code: /tcl/0-acs-init.tcl and /packages/acs-kernel/bootstrap.tcl
This document describes the startup (bootstrapping) process for an AOLserver running OpenACS. -
+
+ + +
Before OpenACS 3.3, the OpenACS startup process was extremely simple: after AOLserver
performed its internal initialization (reading the configuration file,
loading shared libraries and module code, etc.) it scanned through the Tcl
library directory (generally /var/lib/aolserver/yourservername/tcl),
sourcing each file in sequence.
-
While this overall structure for initialization is still intact, package +
+ +While this overall structure for initialization is still intact, package management has thrown a wrench into the works - there are a few extra things -to do during initialization, most notably:
Examine the OpenACS file tree for files that should not be present in OpenACS +to do during initialization, most notably:
+ +Examine the OpenACS file tree for files that should not be present in OpenACS (i.e., that were once part of the OpenACS distribution but have since been removed).
Scan the /packages directory for new packages.
Initialize enabled packages by sourcing their *-procs.tcl
-and *-init.tcl files.
+and *-init.tcl files.
This document examines in detail each of the steps involved in AOLserver/OpenACS startup. -
As soon as the nsd daemon is executed by the init
process (or otherwise), AOLserver reads its configuration file and
chroots itself if necessary. It then loads shared libraries
indicated in the .ini file (e.g., the Oracle driver and
nssock), and sources Tcl module files (generally in
/home/aol30/modules/tcl). This step is, and has always been, the
same for all AOLservers, regardless of whether they are running OpenACS.
-
Next AOLserver sources, in lexicographical order, each file in the +
+ +Next AOLserver sources, in lexicographical order, each file in the
/tcl directory. The first such file is
0-acs-init.tcl, which doesn't do much directly except to
determine the OpenACS path root (e.g., /var/lib/aolserver/yourservername)
by trimming the final component from the path to the Tcl library directory
(/var/lib/aolserver/yourservername/tcl). But
0-acs-init.tcl's has an important function, namely sourcing
-/packages/acs-core/bootstrap.tcl, which does the following:
Initialize some NSVs used by the core. These NSVs are
+/packages/acs-core/bootstrap.tcl, which does the following:
Initialize some NSVs used by the core. These NSVs are
documented in /packages/acs-core/apm-procs.tcl - no need to
worry about them unless you're an OpenACS core hacker.
@@ -82,8 +111,16 @@
Verify that the core has been properly initialized by checking for the existence of an NSV created by the request processor initialization code. If it's not present, the server won't be -operational, so we log an error.
+operational, so we log an error.
At this point, bootstrap.tcl is done executing. AOLserver
proceeds to source the remaining files in the /tcl directory
(i.e., unpackaged libraries) and begins listening for connections.
-
($Id$)
+