Do not call systemctl from script in service file about gluster-containers

[humblec]

/assign @@SaravanaStorageNetwork

[humblec]

@phlogistonjohn not sure about the systemctl blocking behaviour. Atleast in @SaravanaStorageNetwork testing its not the case. But nothing stopping us from using kill . Leaving for further thoughts from @SaravanaStorageNetwork.

[SaravanaStorageNetwork]

@phlogistonjohn I have tested this locally - have not observed any deadlock issue.
I think one reason may be due the "Type" used.
Here, I am using the Type as simple and hence no issue.

Refer this:
https://unix.stackexchange.com/questions/359941/starting-systemd-service-inside-systemd-service-causes-deadlock

I think it is better to use systemd to stop rather than kill.

[phlogistonjohn]

I think that using systemd various mechanisms to make one service fail if another service fails is probably the right way to go.
But this is just calling systemctl & I'm just nervous that even though it worked for you we might run into issues in other deployments...
If we can get an opinion from @raghavendra-talur that says its OK to keep this approach I'll back off (for now >:-D)

[humblec]

Closing as per previous commment.