public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Robin Roevens <robin.roevens@disroot.org>
To: development@lists.ipfire.org
Subject: [PATCH 0/2] Fix Bug#12935 - status info broken on services.cgi for some addons
Date: Mon, 03 Oct 2022 17:27:17 +0200	[thread overview]
Message-ID: <20221003152720.13140-1-robin.roevens@disroot.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1557 bytes --]

Hi all

This patchset fixes Bug#12935
(https://bugzilla.ipfire.org/show_bug.cgi?id=12935)

Summary:
Addons where the initscript does not match the addon-name and addons with
multiple initscripts are now listed on services.cgi since CU170.
But addonctrl still expected addon name to be equal to
initscript name; Hence starting/stopping/enabling/disabling of such
addons was not possible.
This has always been like that, but that problem was hidden as
services.cgi also did not display those addon services.

After discussing this with Adolf on the Bug report, we concluded that we
should adapt addonctrl to work with the new addon metadata
Services-field instead.

I basically rewrote addonctrl to not only use the new services metadata
but also to have better errorchecking and added the posibility to check
if a service is currently enabled or disabled.
As a result services.cgi no longer has to go checking the precense of
runlevel initscripts, but can just ask addonctrl.
I also added a warning to services.cgi if a runlevel initscript does not
exists, to prevent the user from wondering why he can't enable a
specific service. (Adolf pointed out some services don't install
runlevel initscripts by default)

More details in the bugreport and in the commit-messages of the patches.

Regards
Robin

GIT: [PATCH 1/2] misc-progs: addonctrl: Add support for 'Services'
GIT: [PATCH 2/2] services.cgi: Fix status/actions on services with name !=

-- 
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.


             reply	other threads:[~2022-10-03 15:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 15:27 Robin Roevens [this message]
2022-10-03 15:27 ` Robin Roevens
2022-10-04  9:48   ` Michael Tremer
2022-10-03 15:27 ` [PATCH 1/2] misc-progs: addonctrl: Add support for 'Services' metadata Robin Roevens
2022-10-03 17:10   ` Adolf Belka
2022-10-04 10:28   ` Michael Tremer
2022-10-04 11:40     ` Robin Roevens
2022-10-04 23:09       ` Robin Roevens
2022-10-07 10:35         ` Michael Tremer
2022-10-03 15:27 ` [PATCH 2/2] services.cgi: Fix status/actions on services with name != addon name Robin Roevens
2022-10-03 17:09   ` Adolf Belka
2022-10-04  9:51   ` Michael Tremer
2022-10-04 10:33     ` Robin Roevens
2022-10-04 12:49       ` Michael Tremer
2022-10-05 19:43         ` Robin Roevens

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221003152720.13140-1-robin.roevens@disroot.org \
    --to=robin.roevens@disroot.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox