Path: utzoo!utgpu!watserv1!watmath!iuvax!ux1.cso.uiuc.edu!brutus.cs.uiuc.edu!unix.cis.pitt.edu!yahoo
From: yahoo@unix.cis.pitt.edu (Kenneth L Moore)
Newsgroups: comp.unix.questions
Subject: Re: Some core dump questions
Keywords: remember what you have in your .cshrc
Message-ID: <22030@unix.cis.pitt.edu>
Date: 1 Feb 90 20:57:46 GMT
References: <5458@hydra.gatech.EDU> <1990Jan31.070404.17399@athena.mit.edu> <21995@unix.cis.pitt.edu> <555@prcrs.UUCP>
Reply-To: yahoo@unix.cis.pitt.edu (Kenneth L Moore)
Organization: Univ. of Pittsburgh, Comp & Info Services
Lines: 32

In article <555@prcrs.UUCP> wrwalke@prcrs.UUCP (William Walker) writes:
>In article <21995@unix.cis.pitt.edu>, yahoo@unix.cis.pitt.edu writes:
>> In article <1990Jan31.070404.17399@athena.mit.edu> jik@athena.mit.edu writes:
	=>=> =>First, how to prevent the creation of core files:
=>=> =>  Doing a "limit coredumpsize 0" in the default .cshrc file *is* the
=>=> =>right way to do it.  If the coredumpsize is limited to 0, the core file
=>=> =>will not be created at all.
=>=> 
=>=> Of course when you need a core, for use with dbx for example, you are up
=>=> THE creek. 
=>=> 
=>
=>read again, mr kamens wrote "default .cshrc file".  that sets it for all users
=>who :
=>	 1- don't know or need to know what a core file is or does.
=>	 2- don't want core files cluttering around
=>
=>to save a core file, just set coredumpsize to some reasonable figure and the
=>defaults are no longer in effect for you.  set it back to 0 and core files
=>are not created again.
=>
=>bill.
=>
=>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
=>   William Walker   ---   uunet!prcrs!wrwalke   ---   530N-3  (703)556-2565
=> NO Santa Claus, I said Mickey Mouse Phone, not IBM-PC Clone.  Oh well, there
=>                    isn't really THAT much difference.
=>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

I thought this was obvious.
-- 
I don't yell and I don't tell and I'm grateful as hell: Benny Hill