Date: Mon, 20 Sep 1999 11:24:17 -0700 From: Jamie Norwood <mistwolf@mushhaven.net> To: Parag Patel <parag@cgt.com> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: App core-files being dumped with 0 size on 3.3-STABLE Message-ID: <19990920112417.A41519@mushhaven.net> In-Reply-To: <634.937850998@pinhead.parag.codegen.com>; from Parag Patel on Mon, Sep 20, 1999 at 11:09:58AM -0700 References: <634.937850998@pinhead.parag.codegen.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 20, 1999 at 11:09:58AM -0700, Parag Patel wrote: > > 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. This is how I always have seen *NIX systems behave... You could write a script based off the find command that you could run once a day that would go through and remove all core files... Jamie > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990920112417.A41519>