lighttpd: Questionable use of invoke-rc.d

Package: init-system-helpers; Maintainer for init-system-helpers is Devuan Dev Team <devuan-dev@lists.dyne.org>; Source for init-system-helpers is src:init-system-helpers.

Reported by: Opty <opty77@gmail.com>

Date: Tue, 1 Apr 2025 12:44:01 UTC

Severity: normal

Tags: debian, moreinfo

Merged with 881, 883, 884

Found in version init-system-helpers/1.65.2devuan1

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.devuan.org
Subject: bug#882: [devuan-dev] bug#882: /etc/logrotate.d/lighttpd: Questionable use of invoke-rc.d
Reply-To: Opty <opty77@gmail.com>, 882@bugs.devuan.org
Resent-From: Opty <opty77@gmail.com>
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: devuan-dev@lists.dyne.org
X-Loop: owner@bugs.devuan.org
Resent-Date: Wed, 02 Apr 2025 13:22:01 +0000
Resent-Message-ID: <handler.882.B882.174360006610833@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
X-Devuan-PR-Message: followup 882
X-Devuan-PR-Package: lighttpd
X-Devuan-PR-Keywords: debian
References: <Z-wWIAMSDJ_2wbuI@hindley.org.uk> <CAERDJOE5eNxeErD=xLsVPWN5jfodbn06BYHXz5QiCcdz3jmxnQ@mail.gmail.com> <CAERDJOHUES6YsTpgN_fEp8K6mf4oXbMrsZqN0MPsHs+bU5BawA@mail.gmail.com> <20250402141208.2942da15@lorenz.fritz.box> <CAERDJOF5+QSoxQs_5kgNwZONn10o5H7Abg+MaU6-dMKYPikGSA@mail.gmail.com> <CAERDJOE5eNxeErD=xLsVPWN5jfodbn06BYHXz5QiCcdz3jmxnQ@mail.gmail.com>
Received: via spool by 882-submit@bugs.devuan.org id=B882.174360006610833
          (code B ref 882); Wed, 02 Apr 2025 13:22:01 +0000
Received: (at 882) by bugs.devuan.org; 2 Apr 2025 13:21:06 +0000
Delivered-To: bugs@devuan.org
Received: from email.devuan.org [2a01:4f9:fff1:13::5fd9:f9e4]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 02 Apr 2025 13:21:06 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id 95vBBbY57Wf6GgAAmSBk0A
	(envelope-from <opty77@gmail.com>)
	for <bugs@devuan.org>; Wed, 02 Apr 2025 13:20:54 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id F0DE34A8; Wed,  2 Apr 2025 13:20:53 +0000 (UTC)
Authentication-Results: email.devuan.org;
	dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20230601 header.b=NtkHLqlE;
	dkim-atps=neutral
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,
	T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2607:f8b0:4864:20::230; helo=mail-oi1-x230.google.com; envelope-from=opty77@gmail.com; receiver=<UNKNOWN> 
Received: from mail-oi1-x230.google.com (mail-oi1-x230.google.com [IPv6:2607:f8b0:4864:20::230])
	by email.devuan.org (Postfix) with ESMTPS id 2C71B173
	for <882@bugs.devuan.org>; Wed,  2 Apr 2025 13:20:53 +0000 (UTC)
Received: by mail-oi1-x230.google.com with SMTP id 5614622812f47-3fe84963e5fso311865b6e.1
        for <882@bugs.devuan.org>; Wed, 02 Apr 2025 06:20:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1743600051; x=1744204851; darn=bugs.devuan.org;
        h=content-transfer-encoding:cc:to:subject:message-id:date:from
         :in-reply-to:references:mime-version:from:to:cc:subject:date
         :message-id:reply-to;
        bh=4qloF25wpSMfcxoCIA61gShuFHrd5Uana2RKA9BRS10=;
        b=NtkHLqlExJRzYnvDqcLF7T1MQCacUUYoPzB35eRkS/41QC6LQNpsQx9FvSmCpqlh69
         OdRWKerAEZlIfyArTIyQ8RmSXRQf17X8bOePyzFdBc4l3wKZbPQQzhwX0vH3xaRJw5VK
         J5G3ojobCRpmKrl7qj1gCehOpBnh2fXSwG51MmmVnl42svuEcj1Upg2lyCkQY9S12q4e
         xLxv7w3j7RNmFK0hMwdPeOSVFb2dyqPABKUxpoDfXzb8gZSRqv71twu0lbhnE3HvzTeO
         RmMiexvOTbW4+OiyQl7SMNTctRCDmq3ICb31UqLMOXkyDe7EngTK7n4u0bWmrVyPcwlw
         gZvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1743600051; x=1744204851;
        h=content-transfer-encoding:cc:to:subject:message-id:date:from
         :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc
         :subject:date:message-id:reply-to;
        bh=4qloF25wpSMfcxoCIA61gShuFHrd5Uana2RKA9BRS10=;
        b=YEi3eL7OBQ41QMv36UjeUTHoQ247h2PMOBP/69oiCQVyuHY758iN0K6s+ttVISj5Ug
         0UCGuqCBiTHMAqla5Bqz9Xz1/deNAmRmpzNzhgftHWcD4w0imoA98S00UJbfbpX0Brja
         QUy8Unt60xCvkVMZnqFAf3avmWGjoeFx6XA9UV0jsPU4VKI6AOZiRaakBg1NJj+c/kdk
         iOU3qz89ajkHsy5v9eG0Ar9a+BEEEGIydgXKuM83Rb2RQzSapC0L1ZIaiRdLdU+I5ss9
         KSebM7HsD9is7RM8cOn0C8exP+lRJUamTfKOFPp3l6JIer1NCFczkyR8uSdjiHOaMsIP
         7sUQ==
X-Gm-Message-State: AOJu0Ywmit6tEESeBbE/v9vh1VjZcN/JkgW1LJU6zQ1u8hbesaNV+7PH
	L43iSPXZ7/7ZFxz1k//Fj3toTc4I+JNwGE0X7d+WIjfrzdM6Xw+leCJxgioMocJjgNVvLVxOU8v
	4EPXgngVIbL9P8Yr6Q0U8V4+Ue44=
X-Gm-Gg: ASbGncuNINkn1xVqfkHhsHvPRdNEJDVXVL30mUyX+AJpaOH2oDWGnQBbjSHBO3ndpqD
	23+DS42NoMNQ4JGiLcsyPpAiuxsJMHmuCWsSyHhDvfJcEuwVmueKR0gNHBVMPHBPbYd8KnMotsm
	Rd/JXWnU7eBEXSN43oXRjNBTRaNTwtxpcc+ALLGOrNBJJk
X-Google-Smtp-Source: AGHT+IGciCsmXDKnojrUCruP8ubDCnPMetXMtlPCQlT/JiX+i5oPOGMvrjQa8x98qWe6KApoQSjsjaSGo7/L0gz0p04=
X-Received: by 2002:a05:6808:15a8:b0:3fe:af0a:37cd with SMTP id
 5614622812f47-3ff0f3d75e5mr3562715b6e.0.1743600051334; Wed, 02 Apr 2025
 06:20:51 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <CAERDJOF5+QSoxQs_5kgNwZONn10o5H7Abg+MaU6-dMKYPikGSA@mail.gmail.com>
From: Opty <opty77@gmail.com>
Date: Wed, 2 Apr 2025 15:20:39 +0200
X-Gm-Features: AQ5f1JoZ9X0P5XoUsBC9soLtw9XoWF0RqjNDwY-VfgDJcUZANwrGjmmFA75XbwM
Message-ID: <CAERDJOGK-M2sD2e6Vo9xNT=6QA9E3tUqQKf8m7AAqOKTOLtZYA@mail.gmail.com>
To: Lorenzo <plorenzo@disroot.org>
Cc: 882@bugs.devuan.org, Mark Hindley <mark@hindley.org.uk>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 2, 2025 at 2:42 PM Opty <opty77@gmail.com> wrote:
> On Wed, Apr 2, 2025 at 2:12 PM Lorenzo <plorenzo@disroot.org> wrote:
> > Please don't: while this may solve your use case it will break other
> > more common use cases that are currently working.
> > Example:
> > lighttpd installed but disabled by the local admin (K links) but if
> > service wrapper is used instead of invoke-rc.d the logrotate snippet
> > will try to signal lighttpd regardless, which should not happen.
>
> Good, no work for me. :-)
>
> I should have written that I was actually afraid of something like
> that in general but 'service' seemed as the best proposal at that
> time. See also #881.

I recalled why I proposed 'service' and even reported all of these:

"invoke-rc.d and policy-rc.d are precisely interfaces expected to be
used only by maintainer scripts. Anything else done during run-time
should be using some other interface, such as service(8) for example
or an init specific one, otherwise that should be considered a bug."

and

"In case this is a local problem where you have deployed
non-maintainer scripts using invoke-rc.d, then while you fix those,
you could check in policy-rc.d if you are running inside dpkg by
checking if the environment variable DPKG_RUNNING_VERSION is defined
(documented in dpkg(1))."

(see https://bugs.debian.org/804018#25)

Regards,
Opty

Send a report that this bug log contains spam.

Devuan bug report logs - #882 /etc/logrotate.d/lighttpd: Questionable use of invoke-rc.d

Devuan bug report logs - #882
/etc/logrotate.d/lighttpd: Questionable use of invoke-rc.d