Paul Wise dixit:
>> Yes, the procps init script does not have the action reload.
>
>Looks like this is a regression in procps in buster and later.
Hrm. OK, but…
>I've bounced the thread to the procps maintainer and reassigned.
… this isn’t right. This is an RC bug in corekeeper but nōn-RC
in procps because of Policy §9.3.2:
| The "start", "stop", "restart", and "force-reload" options should be
| supported by all init scripts. Supporting "status" is encouraged. The
| "reload" and "try-restart" options are optional.
So I think it’d be better to clone the bugreport, asking procps nicely
to implement “reload” while fixing corekeeper for bullseye first.
bye,
//mirabilos
PS: I was unclear in the previous mail… I found the bug while
crossgrading but was actually installing corekeeper on my
systems recently; apt insisted on remove+install which is
what triggered this.
--
<ch> you introduced a merge commit │<mika> % g rebase -i HEAD^^
<mika> sorry, no idea and rebasing just fscked │<mika> Segmentation
<ch> should have cloned into a clean repo │ fault (core dumped)
<ch> if I rebase that now, it's really ugh │<mika:#grml> wuahhhhhh
