Exit consistently in init scripts for stop on stopped service
-------------------------------------------------------------
Key: BIGTOP-225
URL: https://issues.apache.org/jira/browse/BIGTOP-225
Project: Bigtop
Issue Type: Sub-task
Components: General
Affects Versions: 0.1.0
Reporter: Peter Linnell
Fix For: 0.3.0
CDH init scripts exit with both 0 and 1 when calling stop on a stopped service.
It's common to exit successful when stopping an already stopped service.
LSB agrees with this: "In addition to straightforward success, the following
situations are also to be considered successful: ... running stop on a service
already stopped or not running"
http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
root@node00:~/zookeeper# for file in /etc/init.d/hadoop-*; do $file stop
2>/dev/null >&2; printf "%50s %d\n" $file $?;done
/etc/init.d/hadoop-0.20-datanode 1
/etc/init.d/hadoop-0.20-jobtracker 1
/etc/init.d/hadoop-0.20-namenode 1
/etc/init.d/hadoop-0.20-secondarynamenode 1
/etc/init.d/hadoop-0.20-tasktracker 1
/etc/init.d/hadoop-hbase-master 0
/etc/init.d/hadoop-hbase-regionserver 0
/etc/init.d/hadoop-zookeeper-server 1
root@node00:~/zookeeper# for file in /etc/init.d/hadoop-*; do $file stop
2>/dev/null >&2; printf "%50s %d\n" $file $?;done
/etc/init.d/hadoop-0.20-datanode 1
/etc/init.d/hadoop-0.20-jobtracker 1
/etc/init.d/hadoop-0.20-namenode 1
/etc/init.d/hadoop-0.20-secondarynamenode 1
/etc/init.d/hadoop-0.20-tasktracker 1
/etc/init.d/hadoop-hbase-master 0
/etc/init.d/hadoop-hbase-regionserver 0
/etc/init.d/hadoop-zookeeper-server 1
http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
