Description of problem:
There are three initscripts in extras/init.d, debian, suse, and redhat.  of these, the debian & suse scripts "stop" action only stops the glusterd process, and does not touch running glusterfsd processes.  the redhat script (line 52-53), on the other hand, appears to stop both glusterd & glusterfsd processes.  Is that  right?

Version-Release number of selected component (if applicable):

All?

How reproducible:

Personally, I can only confirm the behavior on debian-derived distros (debian & ubuntu) and it is true that "service glusterd stop" does not kill running glusterfsd processes.

I do not have access to a redhat or suse box to test.

Steps to Reproduce:
1. Create volume
2. Start volume
3. "service glusterd stop"
4. did the glusterfsd process get killed also?
  
Actual results:

On debian/ubuntu only the glusterd process is killed, glusterfsd processes are left alone.

On Redhat?

On Suse?

Expected results:

The expected behavior is that only the glusterd process will be killed by "service glusterd stop", but glusterfsd processes will be left alone.


Additional info:

IMHO there needs to be consensus & consistency across distributions as to what "service glusterd stop" will accomplish.  I think it should only stop glusterd, and leave running glusterfsd processes alone, because those are controlled pool-wide using "gluster volume start/stop" commands.

Thank you!