Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!adobe!heaven!heaven.woodside.ca.us
From: glenn@heaven.woodside.ca.us (Glenn Reid)
Newsgroups: comp.sys.next
Subject: Re: Those ubiquitous core files and saving disk space
Message-ID: <442@heaven.woodside.ca.us>
Date: 2 Mar 91 01:31:45 GMT
References: <23137@hydra.gatech.EDU>
Sender: glenn@heaven.woodside.ca.us
Lines: 24

In article <23137@hydra.gatech.EDU> roy@prism.gatech.EDU (Roy Mongiovi) writes:
> Actually, I've found it immensely helpful to create a /cores directory
> so that all core dumps show up in one place.

I've found it even more helpful to keep my applications from dumping core at  
all when they crash.  If you type the following thing into a Terminal window,  
it should keep core files from getting dumped anywhere:

	localhost> limit core 0

For some reason that I don't fully understand, even though the "limit" command  
is actually built into /bin/csh, this approach seems also to prevent NeXTstep  
applications from leaving large core files.  Core files are only useful for  
debugging, and I'd rather not have them at all (especially when disk space is  
tight).

I'm also curious why the core files are "ubiquitous".  What software are you
people running that dumps core so often?  I rarely have anything crash on my
system.  Just curious.

--
 Glenn Reid				RightBrain Software
 glenn@heaven.woodside.ca.us		NeXT/PostScript developers
 ..{adobe,next}!heaven!glenn		415-851-1785 (fax 851-1470)