On Tue, 16 Jan 2018, Bruno Friedmann wrote:
I'm trying to understand why coredumpctl doesn't want to record software crashes ...
systemd[1]: Created slice system-systemd\x2dcoredump.slice. systemd[1]: Started Process Core Dump (PID 507/UID 0). systemd-coredump[508]: Removed old coredump core.X. 0.f03515004fc34c5d968db505b999985b.1894.1516002511000000.lz4. systemd-coredump[508]: Resource limits disable core dumping for process 28038 (kmail). systemd-coredump[508]: Process 28038 (kmail) of user 1502 dumped core.
I've put what I would call generous settings in /etc/systemd/coredump.conf
[Coredump] Storage=external Compress=yes ProcessSizeMax=8G ExternalSizeMax=16G JournalSizeMax=2G MaxUse=10 KeepFree=5
and /var/lib/systemd/coredump/ is empty
By default on TW we have in tmpfiles.d/systemd.conf
d /var/lib/systemd 0755 root root - d /var/lib/systemd/coredump 0755 root root 3d
I don't understand what I'm doing wrong, nor how to make coredumpctl able to register backtrace ...
In tumbleweed, systemd also respects rlimit. Please check: ulimit -c (default is 0) and adapt it accordingly. Regards Thomas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org