Self TestsChapter 7 Administrative Basics 283Self Test ConfigurationThe self tests feature, and individual self tests, are registered and configured in thecms.cfg file. Self tests can either be “enable” or “disable”, meaning that aparticular self test is listed for either on-demand or start up self test, and it can havetwo states, “nothing” or “critical.”Critical self tests have a semi-colon and the word “critical” after the name of theself-test. Otherwise, nothing is in this place. The server will shut down when acritical self test fails during on demand self tests; the server will not start when acritical self test fails during start up.The currently implemented self-tests are automatically registered and configuredwhen you install a CMS instance. The self tests that are registered and configuredare those associated with which type of subsystem has been configured with thisserver instance.You turn the self test off, or change which self tests are considered critical bychanging those setting in the cms.cfg file. To turn a self test off, you remove fromthe list of self tests that run either on-demand or at start up.Modifying Self Test ConfigurationTo modify the configuration settings for self tests:1. Stop the CMS instance.2. Open the cms.cfg file located in the directory/cms-/config3. To edit the settings for the self test log, edit the entries that begin withselftests.container.logger. These include the following parameters:bufferSize. Specify the buffer size in kilobytes (KB) for the log. The default sizeis 512 KB. For more information, see “Buffered Versus Unbuffered Logging”on page 268. Once the buffer reaches this size, the contents of the buffer areflushed out and copied to the log file.enable. Specify true to enable; false to disable. Only enabled logs actuallyrecord events.
