Index: openacs-4/packages/acs-core-docs/www/bootstrap-acs.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/bootstrap-acs.html,v diff -u -r1.49.2.10 -r1.49.2.11 --- openacs-4/packages/acs-core-docs/www/bootstrap-acs.html 21 Jun 2016 07:44:35 -0000 1.49.2.10 +++ openacs-4/packages/acs-core-docs/www/bootstrap-acs.html 23 Jun 2016 08:32:45 -0000 1.49.2.11 @@ -28,14 +28,14 @@ same for all AOLservers, regardless of whether they are running OpenACS.

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 +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:

  1. 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. +worry about them unless you're an OpenACS core hacker.

  2. Verify the deletion of obsolete OpenACS files. The /tcl directory has evolved quite a bit over the months and @@ -52,14 +52,14 @@ procedure are needed to perform any of the following steps.

  3. Ensure that the database is available by grabbing and -releasing a handle. If we can't obtain a handle, we terminate -initialization (since OpenACS couldn't possibly start up the server without +releasing a handle. If we can't obtain a handle, we terminate +initialization (since OpenACS couldn't possibly start up the server without access to the database).

  4. Register any new packages in the /packages directory. In each directory inside /packages, we look -for a .info file; if we find a package that hasn't yet been -registered with the package manager (i.e., it's been copied there +for a .info file; if we find a package that hasn't yet been +registered with the package manager (i.e., it's been copied there manually), we insert information about it into the database. (The first time OpenACS starts up, no packages will have been registered in the database yet, so this step will registers every single package in the @@ -68,8 +68,8 @@ before they can be used.

  5. Ensure that the acs-kernel package is -enabled. If the OpenACS core isn't initialized, the server -couldn't possibly be operational, so if there's no enabled version of +enabled. If the OpenACS core isn't initialized, the server +couldn't possibly be operational, so if there's no enabled version of the OpenACS core we simply mark the latest installed one as enabled.

  6. Load *-procs.tcl files for enabled @@ -81,7 +81,7 @@

  7. 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 +initialization code. If it's not present, the server won't be 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