On 2026-09-23 14:36 -0400, Frank McCormck wrote:
> On 2026-09-23 10:22, Greg Wooledge wrote:
>> On Wed, Sep 23, 2026 at 08:49:04 -0400, Frank McCormick wrote:
>>> Updated my Sid installation this morning and I was struck by a warning
>>> partway
>>>
>>> through the job.
>>>
>>> Setting up systemd (262-1)…
>>> Unrecognized signal name "SIGRTMIN+25" at /usr/bin/deb-systemd-invoke line
>>> 179.
>>>
>>>
>>> Well, here's what my (trixie) deb-systemd-invoke script contains:
>>>
>>> if ($action eq "daemon-reload") { $signal = 'SIGHUP'; } else {
>>> $signal = 'SIGRTMIN+25'; } if ($is_system) { system('kill', '-s',
>>> $signal, '1'); } else { system('systemctl', '--quiet', 'kill',
>>> '--kill-whom=main', '--signal', $signal, 'user@*.service'); } The
>>> line in question is the first system() call, with kill -s. At the
>>> very minimum, this deserves a bug report, I would say. It's not
>>> clear to me why the systemd developers think "SIGRTMIN+25" is a
>>> valid
>>> signal name. It's also not clear to me why they're calling an external
>>> kill process instead of using perl's builtin kill function. Either
>>> way, my opinion is that this bug is in systemd, not in procps.
>>>
> When I am back in Debian I will file a bug
Florent Rougon beat you to it in #1148762[1], a fix should be available
with the next mirror push.
Cheers,
Sven
1. https://bugs.debian.org/1148762
