HP Systems Insight Manager 7.3 Installation and Configuration Guide for Linux

Implementation
Changes made to the log.properties file do not take effect until the log manager daemon or
service is restarted. Restart the Systems Insight Manager service.
CAUTION: The queue size should be changed only with extreme care. If the queue is set too
high, the log manager consumes too much system memory.
NOTE: When the Audit Log file reaches the maximum file size, the log is renamed with
MX_LOGROLLFILEEXT extension and a new file is started. If a previous version of the file has
already been renamed with the MX_LOG_ROLLFILEEXT extension, it will be an automatic roll-over
of an audit log file. A roll-over will not occur until a task running is completed. However, after one
hour of exceeding the maximum file size, if the task is not finished, then the audit log file will roll
over to another file.
Procedure 7 Configuring the Systems Insight Manager Audit Log file location
1. Create a file named path.properties under C:\Program Files\HP\Systems
Insight Manager\config.
Create a file named path.properties under /etc/opt/mx/config.
2. Add the following entry in the path.properties file: LOG=/var/opt/mx/logs .
NOTE: /var/opt/mx/logs is listed here as an example. This path is user-defined.
3. Restart the Systems Insight Manager service and Restart the Systems Insight Manager daemons
(mxstop and mxstart). After restarting the services, a new log file named mx.log resides
in the directory specified in path.properties file.
Configuring task results
Systems Insight Manager enables you to set how long entries remain on the Task Results Page after
a task completes.
Short and long task lifetimes
Some task results are kept for a short time, while other task results are kept for a longer time. Tasks
fall into one or the other category based on the type of tool associated with them. Tasks for the
following tools have a short lifetime:
• Web-launch tools
• Tools that run from the mxexec command line using the -O or -o options to save the command
output
• Tools that run X-Window commands
• Tools that specify in their tool definition the “job-log” flag as disabled, including:
Hardware Status Polling◦
◦ Data Collection
◦ Identify Systems
◦ Software Status Polling
◦ Delete Events
◦ System Protocol Settings
◦ Automatic Discovery
Configuring task results 49