[systemd-devel] behavior of stop in case of multiple processes

[Andrei Borzenkov]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

В Wed, 29 Jul 2015 21:17:18 +0200
Michał Zegan <webczat_200 at poczta.onet.pl> пишет:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hello.
> 
> I am trying to use systemd to run wildfly application server. It is
> being run by a shell script that runs a java vm in a separate process.
> So, killing the script does not kill the other process.
> The service is a simple type service, and I am wondering what happens
> there on stop. when the server receives signal sigint or sigterm
> directly it logs some messages about it being stopped. However, when I
> start it and then stop, this does not happen, i get no message as if
> it was killed by sigkill.
> What may happen? the documentation says that the systemd sends sigterm
> to all processes by default (if KillMode=control-group and this is
> probably default), and then sigkill if processes do not respond for a
> configured amount of time.
> In this case sigterm sent to the shell script (the main process)
> causes it to exit, but then appserver is probably sigkilled.
> I know that setting sendSIGKILL to no makes it shudown normally. What
> is going on?

Could you post your unit file and which version of systemd?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlW5m74ACgkQR6LMutpd94xHcgCgquo2XGHk348JRxeXcUHJR/yu
fjcAoJrusCMl/PHMI69cmx2A0p4gkPfV
=qtmw
-----END PGP SIGNATURE-----