Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!msi.umn.edu!noc.MR.NET!gacvx2.gac.edu!gacvx2.gac.edu!scott Newsgroups: comp.sys.next Subject: Core dump sanity Message-ID: From: scott@texnext.gac.edu (Scott Hess) Date: 4 Apr 91 15:08:50 Distribution: world Organization: Gustavus Adolphus College Nntp-Posting-Host: texnext.gac.edu Lines: 41 In release 2.0 of NextStep, NeXT for some reason decided to remove the previous default coredumpsize=0 for Workspace-spawned processes, and replaced it with coredumpsize=16M. While this is fine in some cases, in most (almost all, in fact) it's sort of silly. For instance, not many people have a use for an Icon core, much less a Mathematica core. Admittedly, you can change this back, also you could for the template new-user account. [BTW: I've not been able to figure out what the correct default is for dwrite. Or is there one? I know there is, because _I_ don't get cores while our new users do, but for the life of me I cannot find it, NextAnswers or no -scott] But it's a bother to have to do this, and in most cases people won't remember to. So, what I would like is for people to insert the following code, or something much like it, into their distributed programs. This will cause you program _not_ to dump core if there are problems. Since few (if any) of the users will have the source to debug with anyhow, it's not a loss: #import #import #import @implementation MyApp : App + initialize { struct rlimit rl={ 0, 0}; getrlimit( RLIMIT_CORE, &rl); rl.rlim_cur=0; setrlimit( RLIMIT_CORE, &rl); return self; } @end Later, -- scott hess scott@gac.edu Independent NeXT Developer GAC Undergrad "Simply press Control-right-Shift while click-dragging the mouse . . ." "I smoke the nose Lucifer . . . Banana, banana."