Tcl script which is to run when the master interpreter is created.
Namespaces, variables and packages loaded during this stage will
be copied later on in the startup process, when child
processes are created.
This option is only available at the global level.
The directive ServerInitScript plays a special
role since the script runs within the master interpreter,
an interpreter created before the Apache parent process spawns
the children that actually will serve the requests coming from
the network. During this stage Apache is still running as a
single process, so this is the right place for doing
initializations or loading packages. Since this
script will be running in a single process environment (from the
Apache point of view) ServerInitScript
is also the right place for doing anything needs to avoid
resource concurrency among processes (e.g. the creation and
initialization of an IPC system)