Netscape ENTERPRISE SERVER 6.1, Руководство пользователя

Страница: 242 / 373

Init SAFs
242 Netscape Enterprise Server NSAPI Programmer’s Guide • April 2002 (Draft)
• Native Thread Pools
• CGI
• Error Logging and Statistic Collection
• ACL
• Security
• Chunked Encoding
• Miscellaneous
For an alphabetical list of directives, see Appendix G, “Alphabetical List of
Directives in magnus.conf.”
Init SAFs
The
Init
directives initialize the server, for example they load and initialize
additional modules and plugins, and initialize log files.
The
Init
directives are SAFs, like
obj.conf
directives, and have SAF syntax rather
than the simpler variable value syntax of other
magnus.conf
directives. They are
located in
magnus.conf
because, like other
magnus.conf
directives, they are
executed only once at server startup.
Each
Init
directive has an optional
LateInit
parameter. For the UNIX platform,
if
LateInit
is set to
yes
, the function is executed by the child process after it is
forked from the parent. If
LateInit
is set to
no
or is not provided, the function is
executed by the parent process before the fork. When the server is started up by
user
root
but runs as another user, any activities that must be performed as the
user
root
(such as writing to a root-owned file) must be done before the fork.
Functions that create threads, with the exception of
thread-pool-init
, should
execute after the fork (that is, the relevant
Init
directive should have
LateInit=yes
set).
For all platforms, any function that requires access to a fully parsed configuration
should have
LateInit=yes
set on its Init directive.
NOTE Much of the functionality of the file cache is controlled by a
configuration file called
nsfc.conf
. For information about
nsfc.conf
, see the Netscape Enterprise Server Performance Tuning,
Sizing, and Scaling Guide.