Bug 4978 - Explicitly use tools for init system in our shipped service wrapper script.
Summary: Explicitly use tools for init system in our shipped service wrapper script.
Status: CLOSED WONTFIX
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Misc (show other bugs)
Version: 4.1.1
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.13.0
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-03 11:26 CET by Henrik Andersson
Modified: 2020-09-08 12:54 CEST (History)
0 users

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Henrik Andersson cendio 2014-02-03 11:26:42 CET 
Today we ship a service helper script to start / stop services which was created on bug #4843. This script uses the service which is sipped with the distribution which is a helper script to dispatch actions to distribution specific init system such as upstart / systemd and SysV.

The main problem is that we can not rely on return codes / status / parsed text which raises problems that we do not know when a service is not available or if it just failed to startup. The script we use today just fires and forgets and result can be interpreted on stdout which differs from system to system.

If we identified and used the tools for the specific init system we could have a more controlled execution of our shipped service script and use exit codes for proper programmatic instrumenting.

See bug #4844 for specifics about systemd and compability with SysV.
Comment 1 Pierre Ossman cendio 2020-09-08 12:54:24 CEST 
We've switched to requiring systemd, so these scripts are gone.
Note You need to log in before you can comment on or make changes to this bug.