[systemd-devel] Where does systemd store coredumps?

Aaron Lewis the.warl0ck.1989 at gmail.com
Fri Jun 13 23:52:30 PDT 2014


Thanks Mantas, I have disabled coredump as you suggested.

P.S Yes, there's tons of XS modules that need recompilation, I have
recompiled LibApparmor.so and the issue was solved.

On Tue, Jun 10, 2014 at 4:59 PM, Mantas Mikulėnas <grawity at gmail.com> wrote:
> (Ahh, critical boot components that depend on Perl. And to think people
> complain about systemd.)
>
> systemd installs a /usr/lib/sysctl.d/*-coredump.conf which changes
> kernel.core_pattern so that the dumps are written to the journal.
>
> You can override it through /etc/sysctl.d to put the dumps in, for example,
> /var/log/core.%p.%c or /dev/null.
>
> Usually Perl 5.20 crashes mean that you have some old binary Perl modules
> that haven't been recompiled for 5.20 (usually AUR or CPAN).
>
> --
> Mantas Mikulėnas <grawity at gmail.com>
> // sent from phone
>
> On Jun 10, 2014 11:19 AM, "Aaron Lewis" <the.warl0ck.1989 at gmail.com> wrote:
>>
>> Hi,
>>
>> I have recently experienced a massive coredump at startup.
>>
>> I upgraded perl from 5.18 to 5.20 in Arch Linux, and apparmor loads
>> massive profiles at boot (which depends on perl), so I can't login
>> through tty.
>>
>> I have autologin enabled but no bash prompt, only coredump messages.
>>
>> So I wonder if there's a way to disable coredump? Looks like systemd
>> stores them in /run/log, which filled my shared memory space.
>>
>> --
>> Best Regards,
>> Aaron Lewis - PGP: 0x13714D33 - http://pgp.mit.edu/
>> Finger Print:   9F67 391B B770 8FF6 99DC  D92D 87F6 2602 1371 4D33
>> _______________________________________________
>> systemd-devel mailing list
>> systemd-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/systemd-devel



-- 
Best Regards,
Aaron Lewis - PGP: 0x13714D33 - http://pgp.mit.edu/
Finger Print:   9F67 391B B770 8FF6 99DC  D92D 87F6 2602 1371 4D33


More information about the systemd-devel mailing list