Hi Charles,
On 18/09/2022 15:44, Charles Brown
wrote:
Hi All,
After upgrading to C170, the Addon 'cpufrequtils' shows as a
stopped service on services.cgi page.
See forum post:
https://community.ipfire.org/t/cu-170-testing-list-of-services-is-not-complete-in-the-webgui-status-services/8413/24
Is cpufrequtils incorrectly labeled as a service in the
corresponding /opt/pakfire/db/meta/meta-* file?
In the LFS file cpufrequtils is defined as a service.
There is also an initscript for cpufrequtils which would support it
being a service.
Or do I have something broken (not running) on my system?
However cpufrequtils seems to be working okay -- showing the
cpufreq info on the Status page, and responding as expected to
cpufreq-info and cpufreq-set commands.
The problem on the services page comes from the fact that the
initscript fort cpufrequtils only has one command - start. There is
no stop command and most importantly no status command.
The services page checks the status command and if it is "is
running" then it is shown as running and green and if it is "is not
running" then it is shown as stopped and red. It looks like if the
service has no status command then the status is defined to be
stopped, even though in this case cpufrequtils is "running".
Either someone needs to create some form of status command for
cpufrequtils, if that is feasible or cpufrequtils should not be
listed as a service.
The latter seems to make more sense to me at the moment as a program
that can only be started and nothing else doesn't sound like what we
would normally consider a service.
I will search a bit about cpufrequtils to see if it really should be
considered a service or not.
I would suggest raising this as a bug. Then any further discussion
about if it is really a service or not can be done there and then
appropriate action taken based on the resultant conclusion.
Regards,
Adolf.
-cab
--
Sent from my laptop