+++ 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):
all

How reproducible:
always

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

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:
http://intranet.corp.redhat.com/ic/intranet/InitscriptsSpec.html
http://intranet.corp.redhat.com/ic/intranet/InitscriptGuidelines.html

For an example of the script that returns the error codes correctly and always
runs status see:
http://devserv.devel.redhat.com/~mmarcini/amd

This bug is tracked by 237789.