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. The thing is, if now other apps dump core, you will have to go find them all over the disk. For instance, on my media center/server there are two apps that crash frequently, and which run full time. One of them is on automatic restart, and can crash a dozen times in succession and dump core each time. With the default systemd handling, I know that the cores will be deleted in a week, automatically. I don't need to care much about it. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)