summaryrefslogtreecommitdiff
path: root/units/systemd-vconsole-setup.service.in
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2020-03-05 07:11:09 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2020-03-05 08:13:49 +0100
commit9fd32ff7d363945fbf8fdae0128702b995127558 (patch)
tree3f5887e8ba339ce0ee990224dc55df477858e38b /units/systemd-vconsole-setup.service.in
parent44e5d00603a8faf57bd8a7bece2eceb0c6b566fd (diff)
downloadsystemd-9fd32ff7d363945fbf8fdae0128702b995127558.tar.gz
units: restore RemainAfterExit=yes in systemd-vconsole-setup.service
This reverts the second part of 8125e8d38e3aa099c7dce8b0161997b8842aebdc. The first part was reverted in 750e550eba362096d56a35104c6a32631aa67b8e. The problem starts when s-v-s.s is pulled in by something that is then pulled in by sysinit.target. Every time a unit is started, systemd recursively checks all dependencies, and since sysinit.target is pull in by almost anything, we'll start s-v-s.s over and over. In particular, plymouth-start.service currently has Wants=s-v-s.s and After=s-v-s.s.
Diffstat (limited to 'units/systemd-vconsole-setup.service.in')
-rw-r--r--units/systemd-vconsole-setup.service.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/units/systemd-vconsole-setup.service.in b/units/systemd-vconsole-setup.service.in
index f4178f495a..9042521c9d 100644
--- a/units/systemd-vconsole-setup.service.in
+++ b/units/systemd-vconsole-setup.service.in
@@ -16,4 +16,5 @@ ConditionPathExists=/dev/tty0
[Service]
Type=oneshot
+RemainAfterExit=yes
ExecStart=@rootlibexecdir@/systemd-vconsole-setup