From 4771148bb92ace55eaa6759a53d04a0f2de9b0d2 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Wed, 11 Apr 2012 21:58:33 +0200 Subject: 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. --- units/getty@.service.m4 | 1 + units/serial-getty@.service.m4 | 1 + 2 files changed, 2 insertions(+) (limited to 'units') 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 diff --git a/units/serial-getty@.service.m4 b/units/serial-getty@.service.m4 index fc8b57b93e..d1d14d35e6 100644 --- a/units/serial-getty@.service.m4 +++ b/units/serial-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=vt100 -- cgit v1.2.3-54-g00ecf