+++ This bug was initially created as a clone of Bug #1277533 +++ Description of problem: stop-all-gluster-processes.sh doesn't return correct return status after successful completion. How reproducible: Always. Steps to Reproduce: 1. run "stop-all-gluster-processes.sh" to kill all gluster process 2. # echo $? Actual results: 1 Expected results: 0 --- Additional comment from Vijay Bellur on 2015-11-03 09:12:20 EST --- REVIEW: http://review.gluster.org/11739 (extras: Exit with SUCCESS if no processes to stop) posted (#7) for review on master by Ramesh N (rnachimu) --- Additional comment from Vijay Bellur on 2015-11-03 09:38:44 EST --- REVIEW: http://review.gluster.org/11739 (extras: Exit with SUCCESS if no processes to stop) posted (#8) for review on master by Ramesh N (rnachimu)
[root@ninja ~]# /usr/share/glusterfs/scripts/stop-all-gluster-processes.sh ; echo $? sending SIGTERM to process 8948 sending SIGTERM to process 8904 sending SIGTERM to process 21469 sending SIGTERM to process 28853 0 [root@ninja ~]# [root@ninja ~]# gluster --version glusterfs 3.7.5 built on Nov 24 2015 02:22:29 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU General Public License. [root@ninja ~]#