
472 Chapter 10
Tuning, Troubleshooting, Security, and Maintenance
System Maintenance
exit
Maintaining the HP OpenView Platform
❏ Erase the trap daemon logfile /var/opt/OV/log/trapd.log if you
no longer need the entries. A large trapd.log can reduce the
performance of ITO. A backup file
/var/opt/OV/log/trapd.log.old is provided.
For detailed information about system maintenance in HP OpenView,
see the HP OpenView Network Node Manager Administrator’s
Reference.
Maintaining ITO Directories and Files
❏ Do not clean up the mgmt_sv directory
/var/opt/OV/share/tmp/OpC/mgmt_sv because it contains
important runtime data. You can cleanup this directory if you are
unable to use another solution or there are too many unprocessed and
old messages.
❏ If you no longer need the logfiles, you should backup and then erase
the continuously growing ITO software
installation/update/de-installation logfile
/var/opt/OV/log/OpC/mgmt_sv/install.log. The logfile
inst_err.log and inst_sum.log do not continuously grow
because they are generated for each ITO software (de-)installation
and/or update.
❏ You should backup and then erase the ITO error/warning logfile
/var/opt/OV/log/OpC/mgmt_sv/opcerror and its backups. ITO
uses an automatic backup logfile mechanism having up to four files. If
the opcerror logfile size is greater than 1 MB, ITO automatically
performs the following:
• if existent: move opcerro2 to opcerro3
• if existent: move opcerro1 to opcerro2
• move opcerror to opcerro1