Hi, After running an update on my server, a private application crashed when told to exist. This was expected, but it dumped a huge core, then compressed it, which took several minutes, during which time I had to wait before rebooting, or it would probably stall:
Isengard:~ # ls -lh /var/lib/systemd/coredump total 2,1G -rw-r----- 1 root root 32M Aug 17 20:28 .#core.Kodi_MovistarTV.1000.50e69b420ce4463dab76ed6532adb941.21327.1502994490000000.xz17cedf1c2919f899 -rw-r----- 1 root root 153M Aug 17 20:28 .#core.Kodi_MovistarTV.1000.50e69b420ce4463dab76ed6532adb941.21327.1502994490000000c1fb45b2282ac57c -rw-r-----+ 1 root root 1,8G Aug 17 20:26 core.Kodi_MovistarTV.1000.50e69b420ce4463dab76ed6532adb941.22507.1502992827000000.xz -rw-r-----+ 1 root root 13M Aug 17 20:01 core.kodi\x2ebin.1000.50e69b420ce4463dab76ed6532adb941.1999.1502992785000000.xz -rw-r-----+ 1 root root 11M Aug 17 05:53 core.kodi\x2ebin.1000.50e69b420ce4463dab76ed6532adb941.21167.1502941816000000.xz Isengard:~ #
Notice the huge size, 1.8 GB. The questions are: can I choose compress options, so that it compresses faster and less? Can I configure not to try dump core of certain named processes? I see the configuration is done in "coredump.conf" (/etc/systemd/coredump.conf, but I don't see there I can configure any of it. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)