Path: utzoo!attcan!uunet!wuarchive!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
Message-ID: <22032@unix.cis.pitt.edu>
Date: 1 Feb 90 21:12:15 GMT
References: <9459@ttidca.TTI.COM> <5458@hydra.gatech.EDU> <1990Feb1.165952.24382@athena.mit.edu>
Reply-To: yahoo@unix.cis.pitt.edu (Kenneth L Moore)
Organization: Univ. of Pittsburgh, Comp & Info Services
Lines: 36

In article <1990Feb1.165952.24382@athena.mit.edu> jik@athena.mit.edu (Jonathan I. Kamens) writes:
>In article <9459@ttidca.TTI.COM>, paulb@ttidca.TTI.COM (Paul Blumstein) writes:
=>=> You were on the right track, but didn't make it small enough.=
=>=> 	limit coredump 0
=>=> under csh will do what you want.  The neat thing is that the bombed
=>=> program will terminate faster since it doesn't have to format the
=>=> dump before it terminates.  You probably got confused by the man page which
=>=> implies that 0 = unlimited.  Actually, I don't know how to set it back to
=>=> unlimited.
=>
=>    % unlimit coredumpsize
=>
=>  Actually, all you really have to type is "unlimit co", since
=>unambiguous abbreviations are permitted by the shell (which is why
=>"limit coredump 0" works).
=>
=>Jonathan Kamens			              USnail:
=>MIT Project Athena				11 Ashford Terrace
=>jik@Athena.MIT.EDU				Allston, MA  02134
=>Office: 617-253-8495			      Home: 617-782-0710

actually all you have to do is type "uc"

assuming you have: 

alias uc unlimit coredumpsize 

in your .cshrc

which would be reasonable if you (as I do) have:

limit coredump 0

in your .cshrc
-- 
I don't yell and I don't tell and I'm grateful as hell: Benny Hill