projects / systemd / .git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 07697d7) | patch
service: a cgroup empty notification isn't reason enough to go down
authorLennart Poettering <lennart@poettering.net>
Wed, 27 Sep 2017 17:56:57 +0000 (19:56 +0200)
committerLennart Poettering <lennart@poettering.net>
Mon, 2 Oct 2017 10:58:42 +0000 (12:58 +0200)
commit3c751b1bfaf734db09256a5631f1f9ce75cf0d35
treee7da759e69a0869cc97350a83172545723b06a38tree | snapshot
parent07697d7ec501ccca25281b30c26b4b2dcbc357e7commit | diff
service: a cgroup empty notification isn't reason enough to go down

The processes associated with a service are not just the ones in its
cgroup, but also the control and main processes, which might possibly
live outside of it, for example if they transitioned into their own
cgroups because they registered a PAM session of their own. Hence, if we
get a cgroup empty notification always check if the main PID is still
around before taking action too eagerly.

Fixes: #6045
src/core/service.c diff | blob | history
https://github.com/systemd/systemd.git