Chris Evich 9be2a6f908 Prevent podman varlink socket fight ... When enabled, it's desired for the podman-varlink process to startup on boot or upon socket-activation, whichever happens first. However, with `KillMode=none` systemd will never kill any podman-varlink processes. This makes it easily possible for multiple podman-varlink processes to be running, and fight each other to service a single socket. --- For example: Prior to this commit, this will result in four podman-varlink processes being run: ``` systemctl enable io.podman.socket systemctl enable io.podman.service systemctl start io.podman.socket systemctl start io.podman.service systemctl start io.podman.service ``` Fix this by setting `KillMode=process` and `TimeoutStopSec=30` (default is 90). This results in podman-varlink exiting on its own after a minute of being idle (--timeout=60000). Alternatively, systemd will manage the service stop by sending a SIGTERM, then if podman-varlink has not exited within `TimeoutStopSec`, a SIGKILL will be sent. Signed-off-by: Chris Evich <cevich@redhat.com>		2019-09-12 11:21:20 -04:00
..
io.podman.service	Prevent podman varlink socket fight	2019-09-12 11:21:20 -04:00
io.podman.socket	Prevent podman varlink socket fight	2019-09-12 11:21:20 -04:00
podman.conf	Tighten the security on the podman varlink socket	2018-05-19 07:47:03 +00:00