HP3000-L Archives

August 2002, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Goetz Neumann <[log in to unmask]>
Reply To:
Goetz Neumann <[log in to unmask]>
Date:
Fri, 2 Aug 2002 02:31:42 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
Chris Schofield wrote:
>
> Hi
>
> We have a system that is using a lot of disc space.  After a lot of
> investigation I find the two following files
>
> -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
>
> What are these files ?  Can I purge them ?

in summary, the log#.raw files hold the IO errors that were
previously logged in LOG####.PUB.SYS. You may want to implement
a similar housekeeping routine on them, as with the PUB.SYS files.
they can be configured to switch to a new file at a certain size.

the second file is an activity log of a MESA (diagnostics) daemon,
it should be purged from time to time.

If any of these files shows a rather rapid growth, then you might
want to get them analysed by your RC. If they grow too large they
can cause performance issues. Yours are already rather large

ITRC doc KBRC00010216 should answer your questions in more detail.

HTH,
Goetz.

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

ATOM RSS1 RSS2