Andrei Borzenkov wrote:
20.05.2018 14:12, Per Jessen пишет:
Andrei Borzenkov wrote:
20.05.2018 13:36, Per Jessen пишет:
It's been a while since I have reason to, but I need a plain (non-root) user to access his own core dumps, and I've forgotten how that is done?
Is there perhaps a way of reverting to having core dumps written to the working dir?
Just mask /usr/lib/sysctl.d/50-coredump.conf:
ln -s /dev/null /etc/syctl.d/50-coredump.conf
You may need to re-create initrd. It really became rather pain-point ... yes, file is included by dracut in systemd mode, so you need to rebuild initrd. Alternative is to use file that explicitly resets core_pattern to default which surprisingly is just "core" :) Although "core.%p" is probably more widely used.
Thanks. Yeah, that is what I would use. I don't mind rebuilding the initrd, but adding kernel.core_pattern = core.%p to /etc/sysctl.d/somewhere is easier :-)
Looking at the current core_pattern:
# cat /proc/sys/kernel/core_pattern |/bin/false
I wonder where that comes from?
This is explicitly set by systemd on startup with intention that it will be later set by 50-coredump.conf (or whatever). Which means I was wrong - masking this sysctl.d file will leave core dumps disabled instead of leaving them as default.
Oh, joy of undocumented ad hoc settings all over systemd code ...
If it's any comfort, I set core-pattern = code.%p - that does exactly what I wanted! The user has access to core dumps right away, no fiddling with coredumpctl and such. Thanks for your help. -- Per Jessen, Zürich (16.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org