Carlos E. R. wrote:
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.
Well, yes, that works - the ACL takes care of that. -- Per Jessen, Zürich (1.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org