69ab10bee5
When upgrading from an older deployment without the lxc-dnsmaq service unit it's possible for the lxc-dnsmasq process to have been left in a defunct state; this is especially true when upgrading as the background process will have been started as a post-up command within the lxcbr0 interface configuration. If the service is in a defunct state, or running without a valid pid file, the systemd service unit will fail to start. This change ensures systemd will clean up all processes owned by the lxc-dnsmaq user with a limited scope of processes matching a regex of "^dnsmasq" which is only effectuve when the service is not managed by systemd and in a defunct state. Change-Id: If183f0b6dfbe0646384cf3bb3b89bc3901643c1e Signed-off-by: Kevin Carter <kevin.carter@rackspace.com> |
||
|---|---|---|
| .. | ||
| default.conf.j2 | ||
| irqbalance.j2 | ||
| lxc-dnsmasq-systemd-init.j2 | ||
| lxc-net-bridge.cfg.j2 | ||
| lxc-net-redhat-bridge.cfg.j2 | ||
| lxc-net-suse-bridge.cfg.j2 | ||
| lxc-net-suse-routes.cfg.j2 | ||
| lxc-net-suseredhat-postdown.cfg.j2 | ||
| lxc-openstack.apparmor.j2 | ||
| lxc-openstack.conf.j2 | ||
| lxc-system-manage.j2 | ||
| lxc.default.j2 | ||
| sudoers.j2 | ||
| systemd-machined.service.j2 | ||
| systemd-proxy-unit.conf.j2 | ||