Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!snorkelwacker!bloom-beacon!athena.mit.edu!jik
From: jik@athena.mit.edu (Jonathan I. Kamens)
Newsgroups: comp.unix.questions
Subject: Re: Some core dump questions
Message-ID: <1990Feb1.165952.24382@athena.mit.edu>
Date: 1 Feb 90 16:59:52 GMT
References: <9459@ttidca.TTI.COM> <5458@hydra.gatech.EDU>
Sender: news@athena.mit.edu (News system)
Reply-To: jik@athena.mit.edu (Jonathan I. Kamens)
Organization: Massachusetts Institute of Technology
Lines: 19

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