Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!vrdxhq!ms3!msitd32
From: msitd32@ms3.UUCP (Russ Brandon)
Newsgroups: net.unix-wizards
Subject: Re: not getting dump after crash
Message-ID: <383@ms3.UUCP>
Date: Wed, 16-Apr-86 15:36:49 EST
Article-I.D.: ms3.383
Posted: Wed Apr 16 15:36:49 1986
Date-Received: Fri, 18-Apr-86 08:54:44 EST
References: <2321@brl-smoke.ARPA>
Organization: ISN - HIOS, Arlington, Va
Lines: 30
Summary: Saving core after crashes

In article <2321@brl-smoke.ARPA>, kjs%tufts.csnet@csnet-relay.arpa (Kevin Sullivan) writes:
> 
> Our 780 running 4.2 has been crashing with "panic: mchk,"  bet we are not
> getting crash dumps,  which makes it difficult to see what is happening.
> On other kinds of crashes we do not have this problem.  Any hints?  Is there
> a way to manually force a dump before rebooting?
> 

	
	First check your /etc/rc file to see if contains a command
	'/etc/savecore directory_name'. This line causes a core image
	to be saved in the named directory when rebooting after a system
	crash. Also check to make sure that this directory is large 
	enough to handle the core image. You space requirements will be
	(the size of /vmunix) + (the size of memory). 
		
		example:
			if /vmunix is size 286720 on an 8Mbyte system,
			the amount of space needed in the directory
			would be  (286720 + 8000000).

	You may want to dedicate an entire filesystem for this purpose.

	For futher info see savecore(8).

-- 
Russell Brandon		...!seismo!vrdxhq!ms3!RSB
c/o ISN, Crop
1235 Jefferson Davis Hwy
Arlington, Va. 22202