Log Files

[Waqar Razi]

I have question about some log files. How important and critical are they and if we are doing trimming, how many days of data should be keep in our records.

/var/opt/omni/log/inet.log
/var/stm/logs/os/log96.raw (There are many log files like log90.raw, log91.raw and so on)

And files with patch names under /var/adm/sw/patch directory.

Can some one give me advice?

[Dennis Handly · Accepted solution]

Do not delete anything under /var/adm/sw/patch, otherwise you won't be able to patch.
You can commit patches or use cleanup(1m).

[Torsten.]

Don't really know about "omni" - could be backup software related.

The stm logs are rotated, so you may consider to remove the oldest.

Never touch any file in /var/adm/sw/patch - use *ONLY* cleanup:

man cleanup

[Waqar Razi]

Wat are the stm logs?

[Pete Randall]

Yes, the /var/opt/omni stuff is from Omniback - or Data Protector as it's now called. I would be cautious about deleting them. They may well be crucial to Data Protector operation.


Pete

[Torsten.]

STM = support tools manager - the online diagnostics.

see

2.2 OnlineDiag - EMS Hardware Monitors and Support Tools Manager (STM)

on

http://docs.hp.com/en/diag.html#2%20Online%20Diagnostics

[Pete Randall]

Hmmmmm. I just looked at my /var/opt/omni/log/inet.log and it looks like a pretty trivial record of activity. I would think you could safely null it out:

> /var/opt/omni/log/inet.log


Pete

[James R. Ferguson]

Hi Wagar:

Using 'cleanup -c 1' may return considerable space in '/var'. The 'cleanup' utility is a friendly frontend to 'swmodify' to commit patches in '/var/adm/sw'. It is a safe way to manage this directory. A committed patch is one whose roll-back state no longer exists. Removing this data gains space at the expense of not being able to restore a previous patch state. The 'cleanup -c 1' leaves at least one previous state available.

Reagrds!

...JRF...

[Prashanth Waugh]

Hi,

My suggestion is take the backup first. then trim it.

Regards
Atul