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
On 10/23/2013 03:09 PM, Michael Cronenworth wrote:
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
On Wed, 2013-10-23 at 09:09 -0500, Michael Cronenworth wrote:
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
On 10/23/2013 08:25 AM, Simo Sorce wrote:
On Wed, 2013-10-23 at 09:09 -0500, Michael Cronenworth wrote:
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
On 10/23/2013 04:09 PM, Michael Cronenworth wrote:
Should systemctl stop foo.service stop all parent and child service
processes?
systemd allows this to be configured in the service's unit file.
See man systemd.kill. glusterd.service uses KillMode=process.
Michal
--
devel mailing list
On 10/23/2013 04:25 PM, Simo Sorce wrote:
If glusterfs feels people need to run the bricks and the main daemons
separately then they should probably split service files and have a
dependency to bring one up when the other comes up, yet still be allowed
to take the daemon down w/o taking down the
On 10/23/2013 11:09 AM, Miroslav Suchý wrote:
On 10/23/2013 04:25 PM, Simo Sorce wrote:
If glusterfs feels people need to run the bricks and the main daemons
separately then they should probably split service files and have a
dependency to bring one up when the other comes up, yet still be
Kaleb KEITHLEY wrote:
Maybe people could be bothered to actually look at what's in the package?
There already is a separate glusterfsd.service file.
That unit file does not stop bricks either.
Perhaps I need to file the bug against the glusterfsd unit file?
--
devel mailing list
On 10/23/2013 11:57 AM, Michael Cronenworth wrote:
Perhaps I need to file the bug against the glusterfsd unit file?
Yes, you should certainly do that.
--
Kaleb
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of
