Should "systemctl stop foo.service" stop all parent and child service processes?
Example: GlusterFS starts a service daemon (glusterd) and a brick daemon
(glusterfsd). When a user issues "systemctl stop glusterd" the service daemon is
stopped but the brick daemon is left running.
I have recently learned that it is expected behavior[1], but this seems to be a
defeat of the purpose of the stop command. What is @devel thoughts?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1022542#c1
[2] I did not contact JoeJulian as I feel this is a Fedora issue and not a
GlusterFS issue.
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
