Netscape Certificate Management System 6.2, Administrator'S Manual

Page: 281 / 874

Self Tests
Chapter 7 Administrative Basics 281
Self Test Configuration
The self tests feature, and individual self tests, are registered and configured in the
cms.cfg
file. Self tests can either be “enable” or “disable”, meaning that a
particular self test is listed for either on-demand or start up self test, and it can have
two states, “nothing” or “critical.”
Critical self tests have a semi-colon and the word “critical” after the name of the
self-test. Otherwise, nothing is in this place. The server will shut down when a
critical self test fails during on demand self tests; the server will not start when a
critical self test fails during start up.
The currently implemented self-tests are automatically registered and configured
when you install a CMS instance. The self tests that are registered and configured
are those associated with which type of subsystem has been configured with this
server instance.
You turn the self test off, or change which self tests are considered critical by
changing those setting in the
cms.cfg
file. To turn a self test off, you remove from
the list of self tests that run either on-demand or at start up.
Modifying Self Test Configuration
To modify the configuration settings for self tests:
1.
Stop the CMS instance.
2.
Open the
cms.cfg
file located in the directory
<server_root>/cms-<instance>/config
3.
To edit the settings for the self test log, edit the entries that begin with
selftests.container.logger
. These include the following parameters:
bufferSize. Specify the buffer size in kilobytes (KB) for the log. The default size
is 512 KB. For more information, see “Buffered Versus Unbuffered Logging”
on page 266. Once the buffer reaches this size, the contents of the buffer are
flushed out and copied to the log file.
enable.
Specify
true
to enable;
false
to disable. Only enabled logs actually
record events.