core: when forcibly killing/aborting left-over unit processes log about it
authorLennart Poettering <lennart@poettering.net>
Wed, 20 Jul 2016 09:16:05 +0000 (11:16 +0200)
committerLennart Poettering <lennart@poettering.net>
Wed, 20 Jul 2016 12:35:15 +0000 (14:35 +0200)
commit1d98fef17d5fd746be163b3aac306068ecec3438
treeb772b94319f12f200a499e700666d1bc4cf248cf
parent26f417d3e8dd2522adfdc4c8fed4c36fa40f48fc
core: when forcibly killing/aborting left-over unit processes log about it

Let's lot at LOG_NOTICE about any processes that we are going to
SIGKILL/SIGABRT because clean termination of them didn't work.

This turns the various boolean flag parameters to cg_kill(), cg_migrate() and
related calls into a single binary flags parameter, simply because the function
now gained even more parameters and the parameter listed shouldn't get too
long.

Logging for killing processes is done either when the kill signal is SIGABRT or
SIGKILL, or on explicit request if KILL_TERMINATE_AND_LOG instead of LOG_TERMINATE
is passed. This isn't used yet in this patch, but is made use of in a later
patch.
src/basic/cgroup-util.c
src/basic/cgroup-util.h
src/core/cgroup.c
src/core/scope.c
src/core/service.c
src/core/unit.c
src/core/unit.h
src/test/test-cgroup.c
src/udev/udevd.c