On Fri, Dec 2, 2016 at 7:13 AM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
02.12.2016 01:02, Ruediger Meier пишет:
Also systemd-coredump should respect the ulimit -c settings (That's what
This limit is for kernel. Systemd does not decide whether to create core or not - it just stores (and possibly preprocesses) it if it was created.
the %c argument would be used for). So if you have a 50G process
If core exceeds ulimit -c, it is not created at all and systemd-coredump does not see it. So how exactly it would be useful here?
I stay corrected. Linux kernel ignores ulimit -c when core_pattern is set to pipe; so yes, it is useful and is actually honored by systemd as of version 229 upstream. If this is not included in Leap 42.2, it is good candidate for bug report.
crashing then this core dumper would probably write the whole 50G to disk. I guess the machine would slow down for hours because by default it even uses xz compression.
ProcessSizeMax= The maximum size in bytes of a core which will be processed. Core dumps exceeding this size will be logged, but the backtrace will not be generated and the core will not be stored.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org