Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Rainer Weikusat Newsgroups: comp.os.linux.development.system Subject: Re: Core dumps Date: Tue, 05 Jun 2012 15:03:09 +0100 Lines: 12 Message-ID: <87wr3lvote.fsf@sapphire.mobileactivedefense.com> References: <8bb99d54-c1e4-4c96-9c48-d0cd3d6eeb50@6g2000vbv.googlegroups.com> <87lik8ebbd.fsf@sapphire.mobileactivedefense.com> <87y5o7hxl8.fsf@sapphire.mobileactivedefense.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: individual.net IpfH1CvmrAr+jOGwjlVIKwW+liyG468uvTOEZMoOXj7tdipYDFbxJ08Ipiftx43l0= Cancel-Lock: sha1:qiVJlxdV4q4t5K8FLqET+LZsowQ= sha1:JW2lERsHzDH29Fmo8Aqib0zQvTE= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) Xref: csiph.com comp.os.linux.development.system:432 Jorgen Grahn writes: [...] > The only RHEL installations I've used came with core dumps disabled -- I > tried to convince the sysadm to enable them, but he argued "they are > disabled by default, and I don't want to change that in case they have > a reason for it". It should usually be possible to enable coredumps for all children of a specific (shell) process by increasing the 'soft coreump limit' with ulimit -c.