NetNews Usenet Archive 1992 #19/NN_1992_19.iso/spool/comp/unix/admin/4679

Internet Message Format | 1992-08-27 | 1.8 KB

Xref: sparky comp.unix.admin:4679 comp.unix.questions:10378 comp.unix.shell:3622
Newsgroups: comp.unix.admin,comp.unix.questions,comp.unix.shell
Path: sparky!uunet!munnari.oz.au!manuel!sserve!ccadfa.cc.adfa.oz.au!cjsv
From: [e-mail] (Christopher JS Vance)
Subject: Re: How to prevent a large core-dump
Message-ID: <[e-mail]>
Originator: [e-mail]
Sender: [e-mail]
Organization: Computer Science, University College, UNSW/ADFA, Canberra, Australia
References: <[e-mail]>
Date: Wed, 26 Aug 1992 01:38:00 GMT
Lines: 24

In article <[e-mail]> [e-mail] (Adwin Soos) writes:
| A few weeks or even months ago I have read some discussion about the problem
| of preventing a core-dump. I remember that there were some suggestions on how
| to prevent that a large core-dump will be made.
| This problem is now occurring at our place where someone is writing a large
| program and in some test-cases there is a core dump for more than 60 Mb.
| This person is not using this core to debug it so maybe we can just stop the
| creation of this core for this person.
| Is there someone who can mail me such suggestions?

If you can use csh or tcsh, it may have a builtin 'limit' command.

Otherwise, if you're on a system with setrlimit(2) you can use that,
although you may need to write a small program to make things happen.

A few years ago, I wrote a small C program I called rlimit which does
this sort of thing because our students' programs were so bad that the
vendor's excellent(?) Pascal compiler kept dumping core and exhausting
their disk quotas.

I don't know how more recent Unices do this, since we don't have one I
can check.

-- Christopher