Description of problem: The init script for glusterd fails to stop gluster-nfsd and glutershd. Version-Release number of selected component (if applicable): # rpm -qa | grep glusterfs glusterfs-3.3.0qa38-1.el6.x86_64 glusterfs-fuse-3.3.0qa38-1.el6.x86_64 glusterfs-server-3.3.0qa38-1.el6.x86_64 glusterfs-geo-replication-3.3.0qa38-1.el6.x86_64 glusterfs-rdma-3.3.0qa38-1.el6.x86_64 How reproducible: [root@rhs20b2-01 ~]# service glusterd stop Stopping glusterd: [ OK ] [root@rhs20b2-01 ~]# ps -ef | grep gluste[r] root 4227 1 0 12:47 ? 00:00:00 /usr/sbin/glusterfs -s localhost --volfile-id gluster/nfs -p /var/lib/glusterd/nfs/run/nfs.pid -l /var/log/glusterfs/nfs.log -S /tmp/9ce16084ada949ea8c9a2c6489d28fa7.socket root 4233 1 0 12:47 ? 00:00:00 /usr/sbin/glusterfs -s localhost --volfile-id gluster/glustershd -p /var/lib/glusterd/glustershd/run/glustershd.pid -l /var/log/glusterfs/glustershd.log -S /tmp/4d96ff6dd7024a5e6d0a214eb58b4640.socket --xlator-option *replicate*.node-uuid=5a6b4e6f-3fd4-4a36-9c6c-07b4014f386c After stopping the glusterd service, gluster-nfs and glustershd are still running.
the plan is to work on bug 815483 to not stop any other process other than 'glusterd' when /etc/init.d/glusterd stop is issued.
after http://review.gluster.com/2919 going in, only 'glusterd' process will be stopped in /etc/init.d/glusterd stop is done. Treating this as not a bug.