Bug 237936 - conman init script uses some incorrect exit codes
conman init script uses some incorrect exit codes
Product: Fedora
Classification: Fedora
Component: conman (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Jarod Wilson
Fedora Extras Quality Assurance
Depends On: 237933
  Show dependency treegraph
Reported: 2007-04-26 04:39 EDT by Michal Marciniszyn
Modified: 2014-02-10 18:02 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-26 14:03:45 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michal Marciniszyn 2007-04-26 04:39:27 EDT
+++ This bug was initially created as a clone of Bug #237933 +++

Description of problem:
On several occasions, the script may end up with error code 0 even when the
service is not started. As an example line:
[ ${NETWORKING} = "no" ] && exit 0
and some others. Also the return codes do not obbey our guidlines. Also note,
that the status command of the service should always return correct value, even
if the service itself cannot be started.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. service network stop
2. service conman start/status
3. echo $?
Actual results:

Expected results:
non-zero error code due to our guidlines/status of the service

Additional info:
When fixing this bug, please obbey our init script guidelines and be sure that
status command is run correctly.
Our guidelines are on following two pages:

For an example of the script that returns the error codes correctly and always
runs status see:

This bug is tracked by 237789.
Comment 1 Jarod Wilson 2007-04-26 14:03:45 EDT
Updated project urls and corrected exit codes.

Note You need to log in before you can comment on or make changes to this bug.