core: explain why failing to set up the crash handler is not a real problem

[elogind.git] / units / container-getty@.service.m4.in

diff --git a/units/container-getty@.service.m4.in b/units/container-getty@.service.m4.in
index abc58cbbcb15d85c0e0ec3da3d74826d974d9f5b..512046692915c9a957cfdcf7f804360905fb851b 100644 (file)
--- a/units/container-getty@.service.m4.in
+++ b/units/container-getty@.service.m4.in
@@ -14,9 +14,10 @@ After=rc-local.service
 )m4_dnl
 Before=getty.target
 IgnoreOnIsolate=yes
+ConditionPathExists=/dev/pts/%I
 
 [Service]
-ExecStart=-/sbin/agetty --noclear --keep-baud pts/%I 115200,38400,9600
+ExecStart=-/sbin/agetty --noclear --keep-baud pts/%I 115200,38400,9600 $TERM
 Type=idle
 Restart=always
 RestartSec=0