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

2015-07-30 Thread Michał Zegan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks, tracking it. W dniu 2015-07-30 o 20:41, Andrei Borzenkov pisze: > В Thu, 30 Jul 2015 20:07:03 +0200 Michał Zegan > пишет: > >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > >> Here is a log from appserver.service: appserver.service: Tryin

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

2015-07-30 Thread Andrei Borzenkov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 В Thu, 30 Jul 2015 20:07:03 +0200 Michał Zegan пишет: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Here is a log from appserver.service: > appserver.service: Trying to enqueue job > appserver.service/stop/replace > appserver.service: Inst

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

2015-07-30 Thread Andrei Borzenkov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 В Thu, 30 Jul 2015 19:57:42 +0200 Michał Zegan пишет: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > First, it seems that sighup is NOT sent by default. Yes, sorry, my mistake. > Second, setting SendSIGKILL to no fixes the problem (and that

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

2015-07-30 Thread Michał Zegan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Here is a log from appserver.service: appserver.service: Trying to enqueue job appserver.service/stop/replace appserver.service: Installed new job appserver.service/stop as 16578 appserver.service: Enqueued job appserver.service/stop as 16578 app

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

2015-07-30 Thread Michał Zegan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 First, it seems that sighup is NOT sent by default. Second, setting SendSIGKILL to no fixes the problem (and that should not be needed), that probably means the second process gets sigkill. W dniu 2015-07-30 o 18:23, Andrei Borzenkov pisze: > В Thu, 3

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

2015-07-30 Thread Andrei Borzenkov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 В Thu, 30 Jul 2015 14:51:44 +0200 Michał Zegan пишет: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Actually when I have sent the question I had systemd-222. > now it is 223 and result is the same. > Unit file is at http://webczatnet.pl/web

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

2015-07-30 Thread Michał Zegan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Actually when I have sent the question I had systemd-222. now it is 223 and result is the same. Unit file is at http://webczatnet.pl/webczat/appserver.service W dniu 2015-07-30 o 05:36, Andrei Borzenkov pisze: > В Wed, 29 Jul 2015 21:17:18 +0200 Mich

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

2015-07-29 Thread Andrei Borzenkov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 В Wed, 29 Jul 2015 21:17:18 +0200 Michał Zegan пишет: > -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 separa

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

2015-07-29 Thread Michał Zegan
-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 wo