drop KillMode=process

MariaDB-10.4 onwards included a pam_helper subprocess to help
with the pam authentication module.

If the user is running with Galera there are SST modules that could
be executing.

By dropping KillMode=process this reverts back to control-group to
cover all of these subprocesses. This is what upstream does.

https://jira.mariadb.org/browse/MDEV-25233 suggests moving to
KillMode=mixed, which is probably ok too, but has been tested less.

Cherry-picked from Fedora: 95f558b833?branch=rawhide
Related: #1971248
This commit is contained in:
Daniel Black 2021-04-22 11:42:51 +10:00 committed by Michal Schorm
parent ee0fe005a8
commit 72944367e0
2 changed files with 0 additions and 2 deletions

View File

@ -53,7 +53,6 @@ ExecStartPost=@libexecdir@/mariadb-check-upgrade
# See also bind-address MariaDB option.
PrivateNetwork=false
KillMode=process
KillSignal=SIGTERM
# Don't want to see an automated SIGKILL ever

View File

@ -59,7 +59,6 @@ ExecStartPost=@libexecdir@/mariadb-check-upgrade --defaults-group-suffix=.%I
# See also bind-address MariaDB option.
PrivateNetwork=false
KillMode=process
KillSignal=SIGTERM
# Don't want to see an automated SIGKILL ever