Date: Fri, 3 Sep 1999 18:23:25 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: bsc4093@dcs.napier.ac.uk Cc: bugs@freebsd.org Subject: Re: core dumping Message-ID: <199909040123.SAA10094@vashon.polstra.com> In-Reply-To: <Pine.SO4.4.01.9908282052560.28355-100000@artemis> References: <Pine.SO4.4.01.9908282052560.28355-100000@artemis>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <Pine.SO4.4.01.9908282052560.28355-100000@artemis>, Robin Carey <bsc4093@dcs.napier.ac.uk> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909040123.SAA10094>