From owner-freebsd-questions Wed Oct 11 5: 9:56 2000 Delivered-To: freebsd-questions@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id BFB1B37B502 for ; Wed, 11 Oct 2000 05:09:53 -0700 (PDT) Received: from [128.130.111.77] (taygeta [128.130.111.77]) by vexpert.dbai.tuwien.ac.at (8.9.3/8.9.3) with ESMTP id OAA01727 for ; Wed, 11 Oct 2000 14:09:42 +0200 (MET DST) Date: Wed, 11 Oct 2000 14:09:43 +0200 (CEST) From: Gerald Pfeifer To: freebsd-questions@freebsd.org Subject: Stopping a core dump in progress? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way of stopping a core dump in progress? While usually I do want to examine core dumps, I had a process going nuts and consuming 500+ MB of virtual memory on a box with 256 MB. Writing the core dump over NFS took incredibly long (state nfsaio most of the time). I tried removing the growing core file and sending the crashing process signals 15 and 9, but nothing worked. So, short of disabling core dumps or limiting the coredumpsize, is there a way to address this on a case by case base, by manually stopping the core dump? Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message