summaryrefslogtreecommitdiffstats
path: root/debian/bcfg2.init
diff options
context:
space:
mode:
authorMichael Fenn <fennm@deshawresearch.com>2013-03-28 09:36:21 -0400
committerMichael Fenn <fennm@deshawresearch.com>2013-03-28 09:36:21 -0400
commitb1cd0e1d5b935ca1f3934930e83ea69acca77fb4 (patch)
tree5238e8d5b886d53aacc29ff580d2b9891744e589 /debian/bcfg2.init
parentaacbd15de9d6985dba876337547d73fb4cabfacb (diff)
downloadbcfg2-b1cd0e1d5b935ca1f3934930e83ea69acca77fb4.tar.gz
bcfg2-b1cd0e1d5b935ca1f3934930e83ea69acca77fb4.tar.bz2
bcfg2-b1cd0e1d5b935ca1f3934930e83ea69acca77fb4.zip
Pass through retval from start, stop, status, etc.
The various init scripts have the usual start, stop, and status functions which are called from a case statement. The functions even nicely return various values for success and failure. Unfortunately, those values were not passed all the way back to the calling shell. Previously, the init scripts would return 0 if any of start, stop, or status failed. This commit ensures that they they pass the return value back to the caller. Why does this matter? Well, beyond just being generally good citizens, bcfg2's own chkconfig client tool expects stopped services to return a non-zero exit code when their status function is called. Otherwise it flags the service state as incorrect and tries to stop it on every run.
Diffstat (limited to 'debian/bcfg2.init')
-rwxr-xr-xdebian/bcfg2.init9
1 files changed, 6 insertions, 3 deletions
diff --git a/debian/bcfg2.init b/debian/bcfg2.init
index 4f83adbf6..b2e47b346 100755
--- a/debian/bcfg2.init
+++ b/debian/bcfg2.init
@@ -47,6 +47,7 @@ fi
# Internal variables
BINARY=$(basename $BCFG2)
+RETVAL=0
# Include lsb functions
. /lib/lsb/init-functions
@@ -70,17 +71,19 @@ start () {
case "$1" in
start)
start
+ RETVAL=$?
;;
stop|status)
- exit 0
+ RETVAL=0
;;
restart|force-reload)
start
+ RETVAL=$?
;;
*)
echo "Usage: $0 {start|stop|status|restart|force-reload}"
- exit 1
+ RETVAL=1
;;
esac
-exit 0
+exit $RETVAL