%META:TOPICINFO{author="ChrisBartram" date="1170455610" format="1.1" version="1.1"}%
%META:TOPICPARENT{name="Hp3000Diagnostics"}%
---+ [[Hp3000StmDiagnostics][STM Diagnostic Utilities on the HP3000]]

We have a system that is using a lot of disc space.  After a lot of investigation I find the two following files:

<pre>
 -rw-r--r-- 1 MANAGER.SYS 0 863518032 Aug 1 10:00 ./var/stm/logs/os/log1.raw.cur
 -rw-r--r-- 1 MANAGER.SYS 0 389522548 Aug 1 10:00 ./var/stm/logs/sys/diaglogd_activity_log
</pre>
What are these files ?  Can I purge them ?

---

The following might be helpful.  It's from an article that will appear in the 7.5 Communicator.

*Log files and Performance Problems*
 
Customers should be aware that the STM product collects system 
information and places it into various log files.  As these log files 
grow in size and number, system performance may be negatively 
impacted.  Users should perform regular processes to clear or remove 
the many log files created by STM.  The STM !ResetSysActLog (RSA) 
command should be used regularly to clear the System Activity Log 
(after examining the log contents with the SAL command, of course). 
Several other log files may be seen under the /var/stm/logs/ 
directory.  Users may wish to stop STM with the !STMSHUT.DIAG.SYS 
program, purge various files within these directories, and restart STM 
with the !STMSTART.DIAG.SYS program.  This might be performed as part 
of the Full Backup on a monthly basis.

Special care should be taken not to purge historical logs that may 
provide critical hardware information such as the files under 
/var/stm/logs/os/ of memlog and log<nnnn>.raw.cur.  Users may wish to 
examine the switch-threshold value in the 
/var/stm/config/sys/diaglogd.cfg file. Enabling the switch-threshold 
with a choice of  1000 to 16000 depending on your system should be 
considered.

[[WalterMurray]]


-- Main.ChrisBartram - 02 Feb 2007