" ---------- Původní zpráva ---------- Od: Zbigniew Jędrzejewski-Szmek zbyszek@in.waw.pl Komu: Development discussions related to Fedora <devel@lists.fedoraproject. org> Datum: 5. 12. 2016 21:57:12 Předmět: Re: F26 System Wide Change: Enable coredumpctl by default
"On Mon, Dec 05, 2016 at 02:36:13PM -0500, DJ Delorie wrote:
Jan Kurik jkurik@redhat.com writes:
Note that coredumpctl is intended as a developer tool,
As a developer, I remove abrt and anything else that redirects cores away from my development area. It's really hard to debug a core dump if you can't find the core file.
You still can restore such behaviour pretty easily. Just set the kernel.core_pattern sysctl. "
Please don't set kernel.core_pattern to "core" or any path unless you set the default RLIMIT_CORE to 0.
Otherwise you will get core dump files littered all around your file system.
The default value of RLIMIT_CORE, that was 0 for decades, has been changed to 'unlimited' in systemd-229.
" systemd-coredump+coredumpctl give you pretty easy access to core files, they are just dumped into /var/lib/systemd/coredump/. The advantage is that a) things are logged and can be easily looked up and queried, b) you get a lot of metadata like open files, cgroups, /proc/mountinfo, umask, capability masks, etc., c) a stacktrace is automatically generated and logged locally, d) old coredumps are automatically removed, e) you cannot fill your disk with coredumps. "
You are describing the ABRT coredumping solution, aren't you? :)
No, seriously, I have to admit that coredumpctl is much more popular
and provides great experience for developers.
We did a big mistake when we were trying to preserve the old school coredumping in CWD.
Regards,
Jakub "