From owner-freebsd-bugs Fri Sep 3 18:24:27 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A0AC914DB2 for ; Fri, 3 Sep 1999 18:24:15 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id SAA06649; Fri, 3 Sep 1999 18:23:26 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA10094; Fri, 3 Sep 1999 18:23:25 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Fri, 3 Sep 1999 18:23:25 -0700 (PDT) Message-Id: <199909040123.SAA10094@vashon.polstra.com> To: bsc4093@dcs.napier.ac.uk Subject: Re: core dumping In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: bugs@freebsd.org Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article , Robin Carey wrote: > > Whilst running a very small executable, FreeBSD-3.1 decided to pump 110 > megs of core-file into my space restricted H/D :) Your program must have managed to allocate that much memory before it bit the dust. > Apart from the obvious wonderment of why 110 megs of junk was > dumped, I noticed that whilst it was dumping, the entire system was > locked up and all other processes weren't getting any CPU. > > Surely this is a Bad Thing (tm). You can set a limit for core dump sizes with ulimit (sh-like shells) or limit (csh-like shells). If the system determines that the file will exceed the limit, it won't dump it. You can also set the limit in the "/etc/login.conf" file with "coredumpsize". See login.conf(5) for more details. If you change your login.conf file, be sure to follow the instructions in the comment at the top of the file. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message