On 2016-12-02 07:43, Andrei Borzenkov wrote:
On Fri, Dec 2, 2016 at 7:28 AM, Carlos E. R. <> wrote:
%p PID of dumped process %P ??
%P PID of dumped process, as seen in the initial PID namespace (since Linux 3.12)
So %p is the same as %P? The manual I read does not say.
%p is PID in process namespace. Which may or may not be the same as %P.
Ah...
Still, I do not see how to control the permissions of the core files.
Core files created by systemd are expected to be root:root with permissions 640 and additional ACL to allow process owner to read them.
Yes, I saw the ACLs later
Why is it not sufficient and how you want to change it?
To allow the user to delete his cores.
Welcome to the wonderful world of Unix permissions that force (each) program to jump through the hoops to implement what would normally need a single ACE on corresponding file.
That said, I suppose "coredumpctl delete" patch has some chances to be accepted.
Huh. No, don't expect that one from me. Outside my possibilities ;-)
By the way, I had 4 coredumps of several processes in 2 days on my single 42.2 install. More than I have seen in months on other releases.
Not sure what you try to say with it.
Just saying :-) That I have seen too many cores in 42.2, something is wrong somewhere. Either 42.2 is not-stable, or 13.1 ate the coredumps without writing them. Or I didn't see where they were. Yes, after noticing there was a core dump, previously one had to seek its location. I like having them in a central point, at least as long as I'm Mr Root ;-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)