On 2016-12-01 14:14, Patrick Shanahan wrote:
* Per Jessen <per@computer.org> [12-01-16 04:08]:
Judging by /proc/sys/kernel/core_pattern, it looks like systemd is now somehow dealing with MY core dump?
# cat /proc/sys/kernel/core_pattern |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %e
It appears to end up in /var/lib/systemd/coredump, where I can read the files, but I cannot delete them? Seems like everybody else can read it - that's surely not right?
This appears to be new in Leap422 - in Leap421, we had just 'core':
# cat /proc/sys/kernel/core_pattern core
appears same in Tw: 08:11 Crash:~ > cat /proc/sys/kernel/core_pattern |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %e
and ends in /var/lib/systemd/coredump/ but as root I can delete them
But not as the user of the application that dumped core. If you are a developer working in some software that dumps core, you can not analyze your own software problem. It can be read by root, and users in the root group. It is easier for the administrator to collect them, delete or send to the developers "outside", but not for the users to do anything. If there is some control about the permissions of cores, it would be better they belonged to a "coredump" group, and make affected users to belong there. Or leave the original permissions, core belongs to the user causing it. I have no idea if/how that is possible. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)