Disabling ABRT?

[Brendan Jones]

On 12/29/2013 05:37 PM, Jan Kratochvil wrote:
> On Sun, 29 Dec 2013 13:17:49 +0100, Richard Fearn wrote:
>> On 29 December 2013 11:29, Brendan Jones <brendan.jones.it at gmail.com> wrote:
>>> Thanks. I had tried this but still no core in the executing directory. Now
>>> I'm not sure where they are going - certainly nowhere in $HOME.
>>
>> Could be a couple of things:
>>
>> 1. The core dump limit for the process could be 0 (i.e. don't write core dumps).
>>
>> 2. The core dumps are written to the cwd of the process at the point
>> where it dies - not necessarily where you run it from. (If you know
>> the PID you could check /proc/<pid>/cwd.)
>
> That is ABRT running/not-running should not have any effect on the normal
> 'ulimit -c' behavior.  It was filed for ABRT and fixed in 2009:
> 	https://bugzilla.redhat.com/show_bug.cgi?id=530637
>
> If stopping/starting ABRT changes anything - that is ABRT behavior is not
> fully transparent - it is a new ABRT bug.
>
>
> Jan
>
Yup. Thanks guys. ulimit -c was 0

ulimit -c unlimited

Fixes my problem. Cores created in the cwd. I would have thought that 
this should be enabled by default in /etc/security/limits.conf in the 
absence of abrt.