--- On Tue, 3/3/09, joseph dolliver <[log in to unmask]> wrote:


> Not that I suggest that but somewhere along the process of being up 
> and running STM , or CSTM is doing something that SLOoooos the
> system down,
> 
**************************************************************((

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

by Walter Murray  (I am pretty sure Walter still lurks here)

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. 

-Craig

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *