mirror of
https://github.com/valitydev/salt.git
synced 2024-11-07 08:58:59 +00:00
3d575e29c4
Fixes #22993. The change is only made for the minion process because, theoretically, only the minion could create the problem described. salt-master and salt-syndic do not theoretically spawn non-salt processes during the lifetime of their processes, whereas salt-minion does this by design. The default behavior for systemd killMode seems to be control-group, which means all processes that share the same control group as the minion process will also be killed by systemd when the minion service is stopped (killed). It is reasonable to expect that activity done on a system by a salt minion should persist beyond the lifetime of the minion process, so let's not kill procs that the minion starts even when the minion exits. |
||
---|---|---|
.. | ||
arch | ||
darwin | ||
ebuild | ||
freeze | ||
macports/ports/sysutils/salt | ||
openbsd | ||
rpm | ||
shar | ||
smartos | ||
solaris | ||
suse | ||
windows | ||
salt-api.service | ||
salt-api.upstart | ||
salt-common.logrotate | ||
salt-master.service | ||
salt-master.upstart | ||
salt-master.upstart.rhel6 | ||
salt-minion.service | ||
salt-minion.upstart | ||
salt-minion.upstart.rhel6 | ||
salt-syndic.service | ||
salt-syndic.upstart | ||
salt-syndic.upstart.rhel6 | ||
salt.bash | ||
salt.postrm | ||
salt.ufw |