Bug 30599 - Support options for different services
Support options for different services
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - System services
UCS 3.1
Other Linux
: P5 enhancement (vote)
: UCS 3.2-x
Assigned To: UMC maintainers
:
Depends on:
Blocks: 30908 13811 16419
  Show dependency treegraph
 
Reported: 2013-02-27 12:35 CET by Erik Damrose
Modified: 2017-08-08 07:09 CEST (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Further conceptual development
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Damrose univentionstaff 2013-02-27 12:35:00 CET
Some services like univention-directory-policy should only show an option to restart them to reload their config (Bug #16419). There is no point in defining the 'programs' key in their service definition as they do not run continuously, and there is no point in defining their startup behavior (automatic, manually, never)

Other services like nfs have multiple programs which should run in order to consider the service 'running'. This is supported basically. But when nfs starts there are multiple forks which result in [nfsd] proccesses to spawn which cannot be detected with the current model.
Comment 1 Moritz Muehlenhoff univentionstaff 2013-05-31 10:43:37 CEST
We will not ship a UCS 3.1-2 release; the next UCS release will be UCS 3.2.

As such, this bug is moved to the new target milestone.
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:38:46 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 3 Stefan Gohmann univentionstaff 2017-08-08 07:09:28 CEST
This issue has been filed against UCS 3.1.

UCS 3.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.