Devuan bug report logs - #881
invoke-rc.d: Policy layer may override runlevel constraint

Full log

🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.devuan.org
From: "Devuan bug Tracking System" <owner@bugs.devuan.org>
To: Opty <opty77@gmail.com>
Subject: bug#882 closed by Mark Hindley <mark@hindley.org.uk> (Re:
 bug#881: invoke-rc.d: Policy layer may override runlevel constraint)
Message-ID: <handler.882.D881.17439286619257.notifdone@bugs.devuan.org>
References: <Z_I9OoxRWQWrCk8F@hindley.org.uk>
 <CAERDJOE5eNxeErD=xLsVPWN5jfodbn06BYHXz5QiCcdz3jmxnQ@mail.gmail.com>
X-Devuan-PR-Message: they-closed 882
X-Devuan-PR-Package: init-system-helpers
X-Devuan-PR-Keywords: debian moreinfo
X-Devuan-PR-Source: init-system-helpers
Reply-To: 882@bugs.devuan.org
Date: Sun, 06 Apr 2025 08:38:05 +0000
Content-Type: multipart/mixed; boundary="----------=_1743928685-9264-3"

[Message part 1 (text/plain, inline)]

This is an automatic notification regarding your bug report
which was filed against the init-system-helpers package:

#882: /etc/logrotate.d/lighttpd: Questionable use of invoke-rc.d

It has been closed by Mark Hindley <mark@hindley.org.uk>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mark Hindley <mark@hindley.org.uk> by
replying to this email.


-- 
881: https://bugs.devuan.org/cgi/bugreport.cgi?bug=881
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems

[Message part 2 (message/rfc822, inline)]

From: Mark Hindley <mark@hindley.org.uk>

To: Opty <opty77@gmail.com>

Cc: 881-done@bugs.devuan.org

Subject: Re: bug#881: invoke-rc.d: Policy layer may override runlevel constraint

Date: Sun, 6 Apr 2025 09:37:14 +0100

Opty,

Thanks,

On Thu, Apr 03, 2025 at 01:16:40PM +0200, Opty wrote:
> > That isn't conventional Debian practice.
> 
> I could continue using the policy layer unmodified, selectively allow
> what I need (extra work) and keep denied the rest
> 
> -or-
> 
> modify invoke-rc.d or rather policy-rc.d to check
> $DPKG_MAINTSCRIPT_NAME (to detect preinst, postinst, prerm or postrm
> script), crosscheck $DPKG_MAINTSCRIPT_PACKAGE vs. $INITSCRIPTID
> (substring of each other) to allow calling other scripts and
> eventually do nothing, maybe ask the administrator.
> 
> Both seem unintentional error- or side-effect-prone.
> 
> I could also just modify invoke-rc.d to skip the querypolicy call in
> case of K link.

I find it hard to see an actionable bug here. I think invoke-rc.d and
policy-rcd-declarative* are behaving as advertised. Your requirements appear
different to what policy-rcd-declarative-deny-all provides. So, as Simon
suggested, you need to write your own policy script to meet your requirements.

Therefore I will close this.

If you think I have missed something, please feel free to reopen.

Thanks

Mark

[Message part 3 (message/rfc822, inline)]

From: Opty <opty77@gmail.com>

To: submit@bugs.devuan.org

Subject: /etc/logrotate.d/lighttpd: Questionable use of invoke-rc.d

Date: Tue, 1 Apr 2025 14:41:25 +0200

Package: lighttpd
Version: 1.4.69-1

/etc/logrotate.d/lighttpd uses invoke-rc.d to notify lighttpd to
reopen logs but it doesn't work when using
policy-rcd-declarative-deny-all so shouldn't the logrotate
configuration snippet use rather 'service' ?

Regards,
Opty

Send a report that this bug log contains spam.