units: allow disabling systemd-coredumpd.service

The new unit is nice, but it might not be appropriate in all scenarios. It
requires a new kernel, which might be known to not be available, and also
changes sysctl kernel.core_pattern at runtime, which might not be desired.
Replace static enablement by a normal [Install] section and add the unit
to presets to enable it by default.

The awkward instructions in the man page are simplified and adjusted.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek
2026-09-08 14:31:45 +09:00
committed by Yu Watanabe
parent 89bf9a9fb4
commit 9c665ee7aa
5 changed files with 7 additions and 8 deletions
+2 -6
View File
@@ -328,12 +328,8 @@
<filename>50-coredump.conf</filename> alone does <emphasis>not</emphasis> override the default
<varname>kernel.core_pattern</varname> on such systems, since <filename>60-coredump.conf</filename> will
still take effect. To set a custom <varname>kernel.core_pattern</varname> of your own on a system where
<filename>systemd-coredumpd.service</filename> is available, you must additionally stop (if currently
running) and mask <filename>systemd-coredumpd.service</filename>:
<programlisting>systemctl mask --now systemd-coredumpd.service</programlisting>
Masking <filename>systemd-coredumpd.service</filename> also prevents
<filename>systemd-coredump-register.service</filename>, which is bound to it, from running and writing
<filename>60-coredump.conf</filename>.</para>
<filename>systemd-coredumpd.service</filename> is active, stop and disable it:
<programlisting>systemctl disable --now systemd-coredumpd.service</programlisting></para>
<para>In order to be used in the <option>--backtrace</option> mode, an appropriate backtrace
handler must be installed on the sender side. For example, in case of