Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!wuarchive!udel!udccvax1!captain
From: captain@vax1.acs.udel.EDU (Jeffrey Kirk)
Newsgroups: comp.unix.xenix
Subject: Re: Core Dumps
Summary: use ln
Message-ID: <5292@udccvax1.acs.udel.EDU>
Date: 11 Dec 89 13:40:39 GMT
References: <591@s5.Morgan.COM>
Reply-To: captain@vax1.acs.udel.EDU (Jeffrey Kirk)
Distribution: usa
Organization: nil
Lines: 12

In article <591@s5.Morgan.COM> amull@Morgan.COM (Andrew P. Mullhaupt) writes:
:I am porting a large program to SCO UNIX System/V 386 r3.2 and
:it has acquired the habit of core dumping here and there. There
:isn't a lot of use in looking at the dumps, which (due to data)
:are about 8 MBytes. I have tried to find a limit I can put on
:the size of core dumps, or a way to pipe them to /dev/null, etc.
:
:I put a file in the directory with the name core, owned by
:root and read only, but the dump still happens. Any ideas?
:

Try: ln /dev/null core, from the directory where you get the dump.