HP Systems Insight Manager 5.2 Installation and Configuration Guide for Linux

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.
To configure the location of the Audit Log:
1. Create a file named path.properties under /etc/opt/mx/config.
2. Restart the HP Systems Insight Manager (HP SIM) daemons (mxstop and mxstart). After restarting
the service, a new log file named mx.log resides in the directory specified in path.properties
file.
Lifetimes for entries on the Task Results Page
Overview
HP SIM 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
• Hardware Status Polling
Tools in this category have no task output, have task output that is saved outside of HP Systems Insight
Manager, or have task results that are unlikely to be of long-term interest. Tasks for all other tools have the
long lifetime.
Frequently scheduled tasks Task results can also be removed from the Task Results Page if a certain
number of task results for a scheduled task accumulate. This setting defaults to 10 instances of a single task.
If more than 10 accumulate on the results page, then the oldest task result for this scheduled task is removed.
Last result tasks A task result is kept indefinitely if it is the last result for a scheduled task. For example, if
a scheduled task is disabled, its final task result is kept indefinitely or until the task is enabled and more task
results accumulate.
Implementation
To configure the short and long task lifetimes, edit the mx.properties file.
• The short lifetime defaults to 30 minutes. To change that time, edit:
MX_JOB_CACHE_TIME_COMPLETED_JOBS=30
• The long lifetime defaults to 30 days. To change that time, edit:
MX_JOB_MAX_COMPLETED_JOB_AGE=30
• Task results for frequently scheduled tasks start to drop off after 10 instances. To change this value,
edit:
MX_JOB_MAX_COMPLETED_JOBS_PER_TASK=10
Lifetimes for entries on the Task Results Page 65