home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.unix.admin:4841 comp.unix.questions:10642 comp.unix.shell:3770
- Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!darwin.sura.net!mlb.semi.harris.com!uflorida!crane.cis.ufl.edu!spp
- From: spp@crane.cis.ufl.edu (Stephen Potter)
- Newsgroups: comp.unix.admin,comp.unix.questions,comp.unix.shell
- Subject: Re: How to prevent a large core-dump
- Message-ID: <36919@uflorida.cis.ufl.edu>
- Date: 2 Sep 92 15:38:13 GMT
- References: <1992Aug25.173056.13401@utwente.nl>
- Sender: news@uflorida.cis.ufl.edu
- Reply-To: spp@crane.cis.ufl.edu (Stephen Potter)
- Followup-To: comp.unix.admin
- Organization: U of Florida. Computer Science Dept.
- Lines: 22
- Nntp-Posting-Host: crane.cis.ufl.edu
-
- In article <1992Aug25.173056.13401@utwente.nl>, soos@math.utwente.nl (Adwin Soos) writes:
- |> Hello netters,
- |>
- |> 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 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?
- |>
- Assuming the person is using some form of csh, why not just place a limit on the
- coredump size....
- Place this in the .cshrc:
- limit coredumpsize 0
-
- This will completely stop coredumps from being written.
-
- --
- "There are worlds out there where the sky is burning. The sea's asleep, and
- the rivers dream. People made of smoke and cities made of sound. Somewhere
- there's danger. Somewhere there's injustice. Somewhere else the tea's getting
- cold. Come on Ace, we've got work to do." -Dr Who, spp@cis.ufl.edu
-