(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 <<a href="mailto:grawity@gmail.com">grawity@gmail.com</a>> // sent from phone <div class="gmail_quote">On Jun 10, 2014 11:19 AM, "Aaron Lewis" <<a href="mailto:the.warl0ck.1989@gmail.com">the.warl0ck.1989@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> 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 - <a href="http://pgp.mit.edu/" target="_blank">http://pgp.mit.edu/</a> Finger Print: 9F67 391B B770 8FF6 99DC D92D 87F6 2602 1371 4D33 _______________________________________________ systemd-devel mailing list <a href="mailto:systemd-devel@lists.freedesktop.org">systemd-devel@lists.freedesktop.org</a> <a href="http://lists.freedesktop.org/mailman/listinfo/systemd-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/systemd-devel</a> </blockquote></div>