[gitlab at salsa.debian.org: Re: debhelper | dh_installinit: Remove the executable bits on package removal / dh_installsystemd: No longer mask system units on package removal (!90)]
Jesse Smith
jessefrgsmith at yahoo.ca
Tue Oct 11 03:21:38 BST 2022
On 2022-10-05 3:32 a.m., Mark Hindley wrote:
> Jesse,
>
> On Tue, Oct 04, 2022 at 10:37:20AM -0300, Jesse Smith wrote:
>> If I'm reading this proposal correctly, what's basically being suggested
>> here is that when insserv is working out dependencies it would just
>> ignore any scripts without execute permissions? And, as a result,
>> startpar wouldn't be asked to run those scripts because they wouldn't
>> show up in the dependency tree.
>
> Yes, or alternatively that insserv is unchanged and startpar ignores scripts
> which have not executable bit. I am not certain which approach is better, but I
> *think* changing insserv makes more sense to me.
>
> No, there isn't a patch anywhere at the moment.
>
> Thanks for looking at it.
>
I've been looking into this a bit more and something which crossed my
mind is I'm wondering if insserv might be lower level than where we want
to handle this change. It seems to me like update-rc.d is likely to be
called if a change is being made to services. Maybe it would make sense
to run "update-rc.d service remove" which should trigger insserv to
rework its dependency tree.
The update-rc.d script could probably just be slightly modified so that
if the target script has either be erased _or_ the target script isn't
executable, then update-rc.d triggers its removal from the boot
sequence. I think this would be a smaller and easier change than getting
insserv to ignore all scripts that are not executable in all circumstances.
Anyone else have thoughts on this?
- Jesse
More information about the Debian-init-diversity
mailing list