HP-UX SysFaultMgmt (System Fault Management) (SFM) Administrator Guide (762798-001, March 2014)

Table 59 DBConfig.xml file configuration parameters (continued)
Description
Range
value
Default
valueParameter
of pages that the DB can hold or DBRecordLifeTime criteria, whichever
is met first.
Argument is NUMBER OF DAYS:30 to
365
365EvwebDBConfig/
ArchedRecordLifetime Indicates the number of days that the events are kept in the history database,
before deleting them permanently.
FMLoggerConfig.xml
The FMLoggerConfig.xml is a common configuration file used to set parameters for log messages
files generated by SysFaultMgmt (System Fault Management) (SFM) and evweb.
SysFaultMgmt (System Fault Management) (SFM) allows the FMLoggerConfig.xml being
modified at anytime and take effect immediately by executing the following command:
# sfmconfig –c /var/opt/sfm/conf/FMLoggerConfig.xml
Table 60 (page 139) describes the parameters to configure
Table 60 FMLoggerConfig.xml file configuration parameters
DescriptionRange valueDefault valueParameter
This tag defines minimum severity of messages written into
log file.
MILESTONE,
INFORMATIONAL,
WARNINGSeverity
The INFORMATIONAL logging severity will generate a lot
of log messages.
WARNING, ERROR,
CRITICAL,
STOPLOGGING
It is strongly advised not to use this severity level for a long
time, as it may result in the usage of huge disk space for
the generated log files.
The default (and recommended) threshold in the runtime
environment is WARNING.
This tag defines about the log filename with absolute path.Possible values
include:
/var/opt/sfm/log/
sfm.log
Target
• STDOUT: All log
messages are
delivered to
console.
• The complete path
to the file where
the log messages
are to be written.
This field defines the maximum size of the log file to the
logging subsystem.
2 KB to 1048576 KB
(1 GB)
20480FileSize
When the log file reaches the maximum file size defined
by “FileSize” tag, the logging subsystem takes the backup
of the current log file and then truncates it.
1 to 103NBackupFiles
This variable defines how many backup files will be
preserved by logging subsystem.
NOTE: The current implementation of the logging mechanism assumes that the path to the log
file (target specified in the configuration file) is already existing.
It means, if the target is specified as “/abc/def/ghi.log”, the path “/abc/def/” should be
already existing, and should be writable by root-user.
FMLoggerConfig.xml 139