summaryrefslogtreecommitdiff
path: root/units/getty@.service.m4
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2012-04-11 21:58:33 +0200
committerLennart Poettering <lennart@poettering.net>2012-04-11 22:37:48 +0200
commit4771148bb92ace55eaa6759a53d04a0f2de9b0d2 (patch)
tree707cf0e315e3e67d54a14af69e7ffc47c7e60f7d /units/getty@.service.m4
parent4590cfe4551c6be80274583019be7a79dca70b43 (diff)
units: exclude gettys from isolate requests
gettys are nowadays mostly autospawned and hence usually subject to being shut down on isolate requests, since they are no dependency of any other unit. This is a bad idea if the user isolates between multi-user.graphical and graphical.target, hence exclude them from the isolation. This has the effect that gettys no longer cleaned up when emergency.target is isolated, which might actualy be considered a feature, even though it is a change from previous behaviour... Note that the one getty that really matters (the one on tty1) is still removed when isolating to emergency.target since it conflicts with emergency.service.
Diffstat (limited to 'units/getty@.service.m4')
-rw-r--r--units/getty@.service.m41
1 files changed, 1 insertions, 0 deletions
diff --git a/units/getty@.service.m4 b/units/getty@.service.m4
index a02838d785..6b931fb871 100644
--- a/units/getty@.service.m4
+++ b/units/getty@.service.m4
@@ -32,6 +32,7 @@ After=rc-local.service
# sure that this is synchronized before getty.target, even though
# getty.target didn't actually pull it in.
Before=getty.target
+IgnoreOnIsolate=yes
[Service]
Environment=TERM=linux