On Sun, 2021-07-18 at 04:31 -0700, Craig Small wrote:
> Which makes zero sense for procps which has no daemon.
The restart action also makes zero sense for things that have no
daemon. In the procps case, the Linux kernel is the software that is
being restarted/reloaded, so reload actually makes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2021-07-16 at 02:49, p...@debian.org wrote:
> Can you elaborate on what you mean by "Using reload is very wrong"?
The scripts should be deliberate and specific. When you use reload you are
saying "don't stop the daemon but do what you do for
On Fri, 2021-07-16 at 12:41 +1000, Craig Small wrote:
> I can add an alias easily enough. Using reload is very wrong so
> corekeeper do the right thing but it's a one line change for procps.
Can you elaborate on what you mean by "Using reload is very wrong"?
--
bye,
pabs
I can add an alias easily enough. Using reload is very wrong so corekeeper
do the right thing but it's a one line change for procps.
- Craig
On Fri, 16 Jul 2021, 12:31 Paul Wise, wrote:
> On Fri, 2021-07-16 at 02:25 +, Thorsten Glaser wrote:
>
> > … this isn’t right. This is an RC bug in
On Fri, 2021-07-16 at 02:25 +, Thorsten Glaser wrote:
> … this isn’t right. This is an RC bug in corekeeper but nōn-RC
> in procps because of Policy §9.3.2:
I still think it is RC as it is a feature regression breaking install
of reverse dependencies in supported configurations (sysvinit).
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
Processing control commands:
> reassign -1 procps 3.3.15-2
Bug #991151 [corekeeper] corekeeper: postrm: invoke-rc.d: initscript procps,
action "reload" failed.
Bug reassigned from package 'corekeeper' to 'procps'.
No longer marked as found in versions corekeeper/1.7.
Ignoring request to alter
Control: reassign -1 procps 3.3.15-2
Control: retitle -1 procps: dropped the reload option from the init script,
breaking corekeeper
Control: affects -1 corekeeper
On Fri, 2021-07-16 at 01:15 +, Thorsten Glaser wrote:
> Yes, the procps init script does not have the action reload.
Looks
Paul Wise dixit:
>On Thu, 2021-07-15 at 21:34 +0200, Thorsten Glaser wrote:
>
>> invoke-rc.d: initscript procps, action "reload" failed.
>
>I don't have this problem on amd64 with systemd,
>can you reproduce it on amd64 with sysvinit?
Yes, the procps init script does not have the action reload.
On Thu, 2021-07-15 at 21:34 +0200, Thorsten Glaser wrote:
> invoke-rc.d: initscript procps, action "reload" failed.
I don't have this problem on amd64 with systemd,
can you reproduce it on amd64 with sysvinit?
I'm thinking of switching to systemd-coredump,
are you interested in adopting
Package: corekeeper
Version: 1.7
Severity: serious
Justification: does not uninstall
X-Debbugs-Cc: t...@mirbsd.de
Removing corekeeper:x32 (1.7) ...
Usage: /etc/init.d/procps {start|stop|status|restart|try-restart|force-reload}
invoke-rc.d: initscript procps, action "reload" failed.
dpkg: error
11 matches
Mail list logo
