add RemainAfterExit=yes to our oneshot systemd services

This is required since systemd 245, without it oneshot services
may get started more than once.

Signed-off-by: Matthias Reichl <hias@horus.com>
This commit is contained in:
Matthias Reichl 2020-03-13 18:41:26 +01:00
parent 244ca937e7
commit 3a5b1f118f
6 changed files with 6 additions and 0 deletions

View File

@ -5,6 +5,7 @@ ConditionPathExists=/sys/class/vtconsole/vtcon1/bind
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/sh -c 'echo 0 > /sys/class/vtconsole/vtcon1/bind'
[Install]

View File

@ -5,6 +5,7 @@ Before=kodi.service
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/sh -c "/usr/bin/brcmfmac-firmware-setup"
[Install]

View File

@ -5,5 +5,6 @@ After=basic.target
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/lib/samba/samba-config
StartLimitInterval=0

View File

@ -5,6 +5,7 @@ After=systemd-tmpfiles-setup.service
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/openssl-config
[Install]

View File

@ -6,6 +6,7 @@ Before=systemd-udevd.service
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=-/usr/bin/udevadm hwdb --update
[Install]

View File

@ -5,6 +5,7 @@ Before=systemd-udevd.service systemd-udev-trigger.service systemd-modules-load.s
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/sbin/kernel-overlays-setup
[Install]