Valentin Rothberg 70801b3d71 generate systemd: custom stop signal ... Commit 9ac5267598 changed the type of the generated systemd units from forking to notify. Parts of these changes was also removing the need to pass any information via the file system (e.g., PIDFILE, container ID). That in turn implies that systemd takes care of stopping the container. By default, systemd first sends a SIGTERM and after a certain timeout, it'll send a SIGKILL. That's pretty much what Podman is doing, unless the container was created with a custom stop signal which is the case when the --stop-signal flag was used or systemd is mounted. Account for that by using systemd's KillSignal option which allows for changing SIGTERM to another signal. Also make sure that we're using the correct timeout for units generated with --new. Fixes: #11304 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>		2021-08-24 10:50:16 +02:00
..
define	Do not leak libpod package into the remote client	2021-03-15 14:02:04 +01:00
generate	generate systemd: custom stop signal	2021-08-24 10:50:16 +02:00
activation.go	pkg/systemd: don't require LISTEN_FDNAMES for socket activation	2021-06-24 09:01:39 -06:00
activation_test.go	pkg/systemd: don't require LISTEN_FDNAMES for socket activation	2021-06-24 09:01:39 -06:00
dbus.go	cgroup-manager-systemd:Fail early if user:rootless and relevent session is not present.	2021-08-17 16:18:54 +05:30