![](https://seccdn.libravatar.org/avatar/7891b1b1a5767f4b9ac1cc0723cebdac.jpg?s=120&d=mm&r=g)
Carlos E. R. wrote:
On 2016-12-01 17:49, Per Jessen wrote:
Patrick Shanahan wrote:
appears same in Tw: 08:11 Crash:~ > cat /proc/sys/kernel/core_pattern |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %e
Somebody knows what means those options?
cer@Telcontar:~> man systemd-coredump No manual entry for systemd-coredump
That man-page _is_ present, I have it.
If we find that out, perhaps we can write our own configuration to that proc file.
You can do that anytime, I have already reverted to "core.%p".
Yep, same here. I find a pretty odd setup, I have to say. What's the point in storing a user-level coredump outside the current dir. Not to mention letting any other user read them.
They can not, unless they are on the root group. At least here.
Ah okay. The core dumps have ACLs, I guess only the user that produced it can read it. I'd still like to understand the reasoning for making this the default. It seems utterly superfluous. Why do user coredumps have to be handled by systemd and stored under /var/lib/systemd/coredump ? -- Per Jessen, Zürich (1.2°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