On 05/12/2025 05:22, D. R. Evans wrote:
Something (not I) must have changed the value in /proc/sys/kernel/
core_uses_pid. I've never messed with any of these /proc/sys/kernel
files, but the behaviour has changed at some point in the not-very-
distant past.
Unsure if the following change is relevant to your case. I can confirm
that apt-listchanges shows it during upgrade to trixie:
/usr/share/doc/systemd/NEWS.Debian.gz
systemd (256~rc3-3) unstable; urgency=medium
- coredumps are now disabled by default via configuration files rather than
an out-of-tree patch (installing the optional systemd-coredump package
will enable them as before). As always, overriding via local drop-ins is
possible if desired. The configuration files that respectively affect
the system systemd instance, the user systemd instances and PAM sessions
are:
/usr/lib/systemd/system.conf.d/10-coredump-debian.conf
/usr/lib/systemd/user.conf.d/10-coredump-debian.conf
/usr/lib/sysctl.d/10-coredump-debian.conf
/etc/security/limits.d/10-coredump-debian.conf
-- Luca Boccassi <[email protected]> Tue, 28 May 2024 00:07:57 +0100
(and <https://lists.debian.org/debian-user/2024/06/msg00126.html> cited it)
I do not see related changelog entries in linux-sysctl-defaults, but the
following is absent on bookworm
/lib/sysctl.d/50-default.conf:kernel.core_uses_pid = 1
