The following log settings in the owcimomd.conf file let you specify where and how much logging occurs, the type of errors logged, and the log size, filename, and format:
If you want to set up debug logging, see Section 6.6, Configuring Debug Logging.
If you want to set up additional logs, see Section 6.7, Configuring Additional Logs.
Specifies the categories the log outputs.
log.main.categories = option
Option |
Use |
---|---|
category_name |
Specifies the categories to be logged using a space delimited list. The categories used in OWCIMOMD are:
For more information about these options, see log.main.level. If specified in this option, the predefined categories are not treated as levels, but as independent categories. No default is available; if a category is not set, no categories are logged and the log.main.level setting is used. |
* |
All categories are logged. This is the default setting. |
log.main.categories = FATAL ERROR INFO
Specifies the components that the log outputs.
log.main.components = option
log.main.components = owcimomd nssd
Specifies the format (text mixed with printf() style conversion specifiers) of the log messages.
log.main.format = conversion_specifier
It is possible to change the minimum field width, the maximum field width, and justification. The optional format modifier is placed between the percent sign (%) and the conversion character. The first optional format modifier is the left justification flag, which is the minus (-) character. The optional minimum field width modifier follows, which is an integer that represents the minimum number of characters to output. If the data item requires fewer characters, it is padded with spaces on either the left or the right, according to the justification flag. If the data item is larger than the minimum field width, the field is expanded to accommodate the data.
The maximum field width modifier is designated by a period (.) followed by a decimal constant. If the data item is longer than the maximum field, then the extra characters are removed from the beginning of the data item (by default) or from the end (if the left justification flag was specified).
Log4j TTCC layout:
"%r [%t] %-5p %c - %m"
Similar to TTCC but with some fixed-size fields:
"%-6r [%15.15t] %-5p %30.30c - %m"
XML output conforming to log4j.dtd 1.2, which can be processed by Chainsaw (if used, this must be on one line; it is split up here for readability):
"<log4j:event logger="%c" timestamp="%d{%s%Q}" level="%p" thread="%t"> <log4j:message>%e</log4j:message> <log4j:locationInfo class="" method="" file="%F" line="%L"/></log4j:event>"
The following is the default:
log.main.format = [%t]%m
Specifies the level the log outputs. If set, the log outputs all predefined categories at and above the specified level.
log.main.level = option
log.main. level = ERROR
Specifies the location of the log file OWCIMOMD uses when the log.main.type setting option specifies that logging is sent to a file.
log.main.location = path_filename
log.main.location = /system/cimom/var/owcimomd.log
Specifies the amount of backup logs that are kept before the oldest is erased.
log.main.backup_index = option
log.main.max_backup_index = 1
Specifies the maximum size (in KB) that the OWCIMOMD log can grow to.
log.main.max_file_size = option
Option |
Use |
---|---|
unsigned _integer_in_KB |
Limits the log to a certain size in KB. |
0 |
Lets the log grow to an unlimited size. This is the default setting. |
log.main.max_file_size = 0
Specifies the type of main log OWCIMOMD uses.
log.main.type = option
log.main.type = syslog