ClearOS Bug Tracker


View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0021641ClearOSapp-services - Services Managerpublic2018-10-01 06:362018-10-24 18:02
ReporterNickH 
Assigned Touser2 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version7.5.0 
Target Version7.5.0 UpdatesFixed in Version7.5.0 Updates 
Summary0021641: Sorting and scope confusion and issues
DescriptionIn the Services (Manager) there is confusion with the sorting. The first set of up/down arrows belong to an untitled column (Running?) and clicking on it sorts into those started and those stopped. The arrows really look like the belong to the Service column but they don't. Sorting by Service works and affects the arrows to the right of the Service column header. Sorting by Startup does nothing obvious except the up and down arrows change when you click on the header. No sorting appears to happen.

Can the Header row be tidied up?

On a separate issue, the scope of the app seems to be indeterminate. It does not cover all the init.d items or the systemd unit files, but it covers a lot of them.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0008041)
user2
2018-10-01 09:11

Hopefully we'll be able to tidy up the header without the need to update the theme.

> On a separate issue, the scope of the app seems to be indeterminate.

It only covers the daemons that are registered with ClearOS. Apps (e.g. OpenVPN) can drop a configlet file in /var/clearos/apps/daemons to register a daemon in the ClearOS API system. In the old days, we used to provide generic hooks into all the start/stop init scripts, but that was removed due to user confusion and not-so-great 3rd party init scripts.
(0008061)
user2
2018-10-01 15:06

Fixed.

Only the "Service Description" and "Service" columns will now be sortable. The theme doesn't have support for specifying sort values, so the "Enable/Disable" and "Startup" columns are not sortable for now.

- Issue History
Date Modified Username Field Change
2018-10-01 06:36 NickH New Issue
2018-10-01 09:03 user2 Status new => confirmed
2018-10-01 09:04 user2 Product Version 7.5.0 Updates => 7.5.0
2018-10-01 09:04 user2 Target Version => 7.5.0 Updates
2018-10-01 09:11 user2 Note Added: 0008041
2018-10-01 15:06 user2 Note Added: 0008061
2018-10-01 15:06 user2 Status confirmed => resolved
2018-10-01 15:06 user2 Fixed in Version => 7.5.0 Updates
2018-10-01 15:06 user2 Resolution open => fixed
2018-10-01 15:06 user2 Assigned To => user2
2018-10-24 18:02 user2 Status resolved => closed