paulb@ttidca.TTI.COM (Paul Blumstein) (02/01/90)
In article <5458@hydra.gatech.EDU> mm42@prism.gatech.EDU (Mark Mitchell) writes:
+Problem #1:
+I'd like to eliminate the creation of core files on a group
+of Sun workstations, except when the user specifically wants
+to get one. The only way I've come up with so far (under csh)
+is to set a limit on the size of core dumps and make it very
+small. This seems awkward at best, so any superior scheme would
+be welcome.
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.
=============================================================================
Paul Blumstein | Is it proper to ask the C.E. fixing your MIDI system
Citicorp/TTI | whether it will ever be able to play the violin again?
Santa Monica, CA +----------------------------------------------------------
{philabs,csun,psivax}!ttidca!paulb or paulb@ttidca.TTI.COM
DISCLAIMER: Don't believe everything I hear or anything you say.barnett@crdgw1.crd.ge.com (Bruce Barnett) (02/01/90)
>> Doing a "limit coredumpsize 0" in the default .cshrc file *is* the >>right way to do it. > In article <21995@unix.cis.pitt.edu>, yahoo@unix (Kenneth L Moore) writes: >Of course when you need a core, for use with dbx for example, you are up >THE creek. Well, most of the time the programmer wants core dumps in a project directory, and not in other directories (unless they like reporting bugs to other people). What you could do is to automatically change your core dump size whenever you change directories to your project directory. Having appropriate entires in the file ./.dir might do it if you redefined your cd command to be: alias cd 'chdir \!*; if ( -f .dir && -o .dir ) source .dir ' -- Bruce G. Barnett <barnett@crd.ge.com> uunet!crdgw1!barnett
jik@athena.mit.edu (Jonathan I. Kamens) (02/02/90)
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
yahoo@unix.cis.pitt.edu (Kenneth L Moore) (02/02/90)
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
yahoo@unix.cis.pitt.edu (Kenneth L Moore) (02/02/90)
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