[systemd-devel] behavior of stop in case of multiple processes
MichaĆ Zegan
webczat_200 at poczta.onet.pl
Wed Jul 29 12:17:18 PDT 2015
-----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?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBAgAGBQJVuSa9AAoJEHb1CzgxXKwYUk8P/2mH7I9bRMGZaIKCBl2Kwgc3
SvzrmZBTzvMiCAQ8vEvOndMBieW1vecw6eXjp6bDJ44QIs0fmOFOxU0J3TJImu/i
Kq3QWB4yP+TacjHuo7rqfenNUOfLkSR+zaErLVfTLN5lOG/EbCN98awtCaSHygsX
jmd9yeWpSYp5Znhj4Fwb6cnQDzNKEMORbyllbFBIFwfC9HSPKiE97tfeDDqlEhZN
5wkIiLGc2BjXWzoYsrsdwPSvStEuXATqfN8/v3Bd+sMWHd1xVeLJS6kwlSdSkNOf
elfM+wp96UXYc6IzjgSWzwfRC7OcCgLiT+hARCSdD2AWpnDix/VVkFGTzYIinTVx
c/Oj0s4+fy7kImfqFb1QnCdD7MWTdIsIQqzYy2Kv9NUYo9amkhp0yzjFc/py9Te3
MEAmi8+vde0UV9plJZyXm/7QAIA627QE0V1++WI2HFF+dq4JUmgGCFEJfEq1dBUl
OjSStVm67mpMNCr1/4mJrjgsmxIdarZpa0J0/jVjJej+qrO5vvhDrpX4XDn4KUZ+
OKj0l/4L2mf3G6wrWV/+pBBp1Twav5gDBQg7LZR5Q8FyOTTWErVGP7yF0V/E5HON
RFjnnEyo5ew+mUCSl9MS1SdgZZRhNsKTAvZTVgXThdyxCusMXMGbG62+xJhRsEw3
yN7w3k1o8F18XDifyab/
=BoaG
-----END PGP SIGNATURE-----
More information about the systemd-devel
mailing list