Carlos E. R. wrote:
On 2018-05-21 16:14, Per Jessen wrote:
Carlos E. R. wrote:
On 2018-05-20 21:19, Per Jessen wrote:
Andrei Borzenkov wrote:
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.
cer@Telcontar:~> cat /proc/sys/kernel/core_pattern |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %e
Ye, I saw something like that suggested, but that leaves a user to have to fiddle with coredumpctl, which afaict requires he is in group 'systemd-journal'. Setting core-pattern = code.%p does exactly what a user needs, without too much fuss.
No, the user doesn't need to fiddle. Just access the directory where the dumps are stored, but currently he doesn't get permission.
I thought that is working as designed. When I googled, I came across this page: https://www.suse.com/de-de/support/kb/doc/?id=7017137 A quick browse suggest coredumpctl is used to access core dumps.
The thing is, if now other apps dump core, you will have to go find them all over the disk.
I guess it might depend on the environment, but we don't have enough for that to be a real problem :-) -- Per Jessen, Zürich (14.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org