From owner-freebsd-stable  Mon Sep 20 11:10: 6 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154])
	by hub.freebsd.org (Postfix) with ESMTP id 54F5615ABC
	for <freebsd-stable@freebsd.org>; Mon, 20 Sep 1999 11:09:59 -0700 (PDT)
	(envelope-from parag@pinhead.parag.codegen.com)
Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1])
	by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id LAA00638
	for <freebsd-stable@freebsd.org>; Mon, 20 Sep 1999 11:09:58 -0700 (PDT)
	(envelope-from parag@pinhead.parag.codegen.com)
To: freebsd-stable@freebsd.org
Subject: App core-files being dumped with 0 size on 3.3-STABLE
X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X
        ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm
X-URL: http://www.codegen.com
Date: Mon, 20 Sep 1999 11:09:58 -0700
Message-ID: <634.937850998@pinhead.parag.codegen.com>
From: Parag Patel <parag@cgt.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I just updated this morning to 3.3-STABLE from 3.2-STABLE, and I have
both my ulimit and /etc/login.conf set so that coredumpsize is zero.
Until 3.3-RELEASE, this prevented any core file from being generated.
In 3.3-RELEASE, I now get a zero-length file.

I see from the CVS log that some cleanup was done to the core-dump code
in kern/kern_sig.c on Sep 1, 1999.  This code has a comment in it saying
that this is now the expected behavior.

So how do I get it to not dump any core file at all?  I do not want
core-dump files being scattered all over my disk-drive like so many
kernel droppings, zero-length or not.  (I find them next to useless.  If
it's a program I'm developing or debugging, I'm generally working on it
anyway, and if it isn't, I throw it out or relaunch if it's netscape.)

Thanks!


	-- Parag Patel


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message