Valentin Rothberg e5c3432944 generate systemd: ExecStopPost for all units ...

Add an `ExecStopPost` run even for units generated without `--new`.
Although it may seem redundant to run `container/pod stop` twice at
first glance, we really need the post run.  If the main PID (i.e.,
conmon) is killed, systemd will not execute `ExecStop` but only the
post one.  We made this obeservation in a customer issue and could
reproduce the behavior consistently.  Hence, the post run is needed
to properly clean up when conmon is killed and it's pretty much a
NOP in all other cases.

Credits to Ulrich Obergfell for throrough and detailed analyses,
which ultimately lead to this fix.

Signed-off-by: Valentin Rothberg <rothberg@redhat.com>

2020-06-17 18:52:44 +02:00

..

generate

generate systemd: ExecStopPost for all units

2020-06-17 18:52:44 +02:00

activation.go

V2 Fix support for tcp://[::]<port> connections

2020-04-17 16:39:59 -07:00

dbus.go

pkg/systemd: add dbus support

2020-03-17 11:29:37 +01:00