summaryrefslogtreecommitdiff
path: root/Makefile.am
diff options
context:
space:
mode:
authorFranck Bui <fbui@suse.com>2016-10-10 12:06:26 +0200
committerLennart Poettering <lennart@poettering.net>2016-10-10 12:06:26 +0200
commit84a69ca9ba49a516c741582c4b2f69b0feb0f020 (patch)
tree324c09cdde62ec1049eca663f2703e2f650934ba /Makefile.am
parent7a9ee77204c2bd18ab6d0236ba17b6439ec76b46 (diff)
unit: drop console-shell.service (#4298) (#4325)
console-shell.service was supposed to be useful for normal clean boots (i.e. multi-user.target or so), as a replacement for logind/getty@.service for simpler use cases. But due to the lack of documentation and sanity check one can easily be confused and enable this service in // with getty@.service. In this case we end up with both services sharing the same tty which ends up in strange results. Even worse, console-shell.service might be failing while getty@.service tries to acquire the terminal which ends up in the system to poweroff since console-shell.service uses: "ExecStopPost=-/usr/bin/systemctl poweroff". Another issue: this service doesn't work well if plymouth is also used since it lets the splash screen program run and mess the tty (at least a "plymouth quit" is missing). So let's kill it for now.
Diffstat (limited to 'Makefile.am')
-rw-r--r--Makefile.am2
1 files changed, 0 insertions, 2 deletions
diff --git a/Makefile.am b/Makefile.am
index f7ae9ff7aa..b09b0cf167 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -524,7 +524,6 @@ dist_systemunit_DATA_busnames += \
nodist_systemunit_DATA = \
units/getty@.service \
units/serial-getty@.service \
- units/console-shell.service \
units/console-getty.service \
units/container-getty@.service \
units/systemd-initctl.service \
@@ -587,7 +586,6 @@ dist_systempreset_DATA = \
EXTRA_DIST += \
units/getty@.service.m4 \
units/serial-getty@.service.m4 \
- units/console-shell.service.m4.in \
units/console-getty.service.m4.in \
units/container-getty@.service.m4.in \
units/rescue.service.in \