1834450 Members
2193 Online
110067 Solutions
New Discussion

Re: Crash information

 
SOLVED
Go to solution
Larry Scheetz
Advisor

Crash information

I am trying to clean up a little space on system and have the following directories and files. I imagine these can be removed since they are a year old?

/var/adm/crash/crash.0
-rw-r--r-- 1 root root 1368 Jul 13 2001 INDEX
-rw-r--r-- 1 root root 8893360 Jul 13 2001 image.1.1.gz
-rw-r--r-- 1 root root 17285327 Jul 13 2001 image.1.2.gz
-rw-r--r-- 1 root root 29474514 Jul 13 2001 image.1.3.gz
-rw-r--r-- 1 root root 43746730 Jul 13 2001 image.1.4.gz
-rw-r--r-- 1 root root 49385188 Jul 13 2001 image.1.5.gz
-rw-r--r-- 1 root root 46118835 Jul 13 2001 image.1.6.gz
-rw-r--r-- 1 root root 6497520 Jul 13 2001 image.1.7.gz
-rw-r--r-- 1 root root 55929237 Jul 13 2001 image.2.1.gz
-rw-r--r-- 1 root root 57723 Jul 13 2001 image.2.2.gz
-rw-r--r-- 1 root root 5983994 Jul 13 2001 vmunix.gz

Thank You
A Happy heart makes the face cheerful
5 REPLIES 5
Steven Mertens
Trusted Contributor
Solution

Re: Crash information

hi,

yes , you can remove the crash.0 dir
without any risk.


Steven
James R. Ferguson
Acclaimed Contributor

Re: Crash information

Hi Larry:

Yes, after a year, I don't think anyone wants to analyze this dump. Leave the '/var/adm/crash/' directory and remove the contents.

Regards!

...JRF...
Tom Geudens
Honored Contributor

Re: Crash information

Hi,
If they are a year old AND you haven't experienced any other crashes since ... you're probably in the clear.
Remove the crash.0 directory (and the bounds file) from /var/adm/crash.

Regards,
Tom
A life ? Cool ! Where can I download one of those from ?
Fragon
Trusted Contributor

Re: Crash information

Manually backup it and then remove! It's safe enough.

-Gerald-
Trond Haugen
Honored Contributor

Re: Crash information

rm -ef /var/adm/crash/crash.0
Do leave the /var/adm/crash/bounds as it's purpose is to increment the number (core.N). This way you can just bu looking in /var/adm/crash/ tell how manny panics the system has had.

Regards,
Trond
Regards,
Trond Haugen
LinkedIn