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: Mark Hindley <mark@hindley.org.uk>
Subject: bug#884: marked as done (/etc/logrotate.d/ulogd2: Questionable
 use of invoke-rc.d)
Message-ID: <handler.884.D881.17439286619257.ackdone@bugs.devuan.org>
References: <Z_I9OoxRWQWrCk8F@hindley.org.uk>
 <CAERDJOGtf3XB+nLODWsNRBYxsYeWkvupTssK-_w=DrdUS08cXQ@mail.gmail.com>
X-Devuan-PR-Message: closed 884
X-Devuan-PR-Package: init-system-helpers
X-Devuan-PR-Keywords: moreinfo debian
X-Devuan-PR-Source: init-system-helpers
Reply-To: 884@bugs.devuan.org
Date: Sun, 06 Apr 2025 08:38:07 +0000
Content-Type: multipart/mixed; boundary="----------=_1743928687-9264-6"

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

Your message dated Sun, 6 Apr 2025 09:37:14 +0100
with message-id <Z_I9OoxRWQWrCk8F@hindley.org.uk>
and subject line Re: bug#881: invoke-rc.d: Policy layer may override runlevel constraint
has caused the Devuan bug report #881,
regarding /etc/logrotate.d/ulogd2: Questionable use of invoke-rc.d
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.devuan.org
immediately.)


-- 
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: Opty <opty77@gmail.com>

To: submit@bugs.devuan.org

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

Date: Tue, 1 Apr 2025 14:47:49 +0200

Package: ulogd2
Version: 2.0.8-1

/etc/logrotate.d/ulogd2 uses invoke-rc.d to notify ulogd2 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

[Message part 3 (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

Send a report that this bug log contains spam.