Since the last friday's synch dmesg is full of
Set kernel.core_pattern before fs.suid_dumpable.
Unsafe core_pattern used with fs.suid_dumpable=2.
Pipe handler or fully qualified core dump path required.
Set kernel.core_pattern before fs.suid_dumpable.
This was not happening before the synch and I don't recall changing anything that could be related to this (as far as I know). Granted I also don't fully understand yet what those messages actually mean since I am very new to Linux.
So far I have only been able to find out that it is most likely realated to systemd (which was updated) and configs related to /usr/lib/sysctl.d/50-coredump.conf or /usr/lib/sysctl.d/60-solus-coredump.conf.
The settings in /usr/lib/sysctl.d/50-coredump.conf look OK (I guess):
`kernel.core_pattern=|/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h
fs.suid_dumpable=2`
But in /usr/lib/sysctl.d/60-solus-coredump.conf it seems to clear one of them:
kernel.core_pattern=
Since I assume /usr/lib/sysctl.d/60-solus-coredump.conf is applied after /usr/lib/sysctl.d/50-coredump.conf it is overwriting this setting and that causes the spam in dmesg (I have no idea tho).
Is this a problem or can it be safely ignored?
