systemd/units/container-getty@.service.m4

#  SPDX-License-Identifier: LGPL-2.1+
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Unit]
Description=Container Getty on /dev/pts/%I
Documentation=man:agetty(8) man:systemd-getty-generator(8)
Documentation=man:machinectl(1)
After=systemd-user-sessions.service plymouth-quit-wait.service
m4_ifdef(`HAVE_SYSV_COMPAT',
After=rc-local.service getty-pre.target
)m4_dnl
Before=getty.target
IgnoreOnIsolate=yes
ConditionPathExists=/dev/pts/%I

# IgnoreOnIsolate is an issue: when someone isolates rescue.target,
# tradition expects that we shut down all but the main console.
Conflicts=rescue.service
Before=rescue.service

[Service]
# The '-o' option value tells agetty to replace 'login' arguments with an
# option to preserve environment (-p), followed by '--' for safety, and then
# the entered username.
ExecStart=-/sbin/agetty -o '-p -- \\u' --noclear --keep-baud pts/%I 115200,38400,9600 $TERM
Type=idle
Restart=always
RestartSec=0
UtmpIdentifier=pts/%I
TTYPath=/dev/pts/%I
TTYReset=yes
TTYVHangup=yes
KillMode=process
IgnoreSIGPIPE=no
SendSIGHUP=yes
Add SPDX license headers to unit files 2017-11-18 19:35:03 +03:00			`# SPDX-License-Identifier: LGPL-2.1+`
			`#`
machinectl: add new command to spawn a getty inside a container 2013-10-31 04:25:44 +04:00			`# This file is part of systemd.`
			`#`
			`# systemd is free software; you can redistribute it and/or modify it`
			`# under the terms of the GNU Lesser General Public License as published by`
			`# the Free Software Foundation; either version 2.1 of the License, or`
			`# (at your option) any later version.`

			`[Unit]`
			`Description=Container Getty on /dev/pts/%I`
man/systemd-getty-generator fix/update * Containers don't use serial-getty@console.service, they use console-getty.service instead, and suppress scanning for kernel or virtualizer consoles. * Nowadays gettys are started on all configured kernel consoles. * except for the line printer console, because that's not a tty. (Seriously. Search CONFIG_LP_CONSOLE). 2017-08-07 20:30:56 +03:00			`Documentation=man:agetty(8) man:systemd-getty-generator(8)`
			`Documentation=man:machinectl(1)`
machinectl: add new command to spawn a getty inside a container 2013-10-31 04:25:44 +04:00			`After=systemd-user-sessions.service plymouth-quit-wait.service`
			m4_ifdef(`HAVE_SYSV_COMPAT',
units: order container and console getty units after getty-pre.target 2017-09-05 15:53:25 +03:00			`After=rc-local.service getty-pre.target`
machinectl: add new command to spawn a getty inside a container 2013-10-31 04:25:44 +04:00			`)m4_dnl`
			`Before=getty.target`
			`IgnoreOnIsolate=yes`
units: make sure container-getty@.service stops restarting when the pts device it is bound to is gone We only want to restart the getty as long as the pts device is still around. As soon as it is gone, the service should be removed to. http://lists.freedesktop.org/archives/systemd-devel/2014-December/026048.html 2014-12-09 04:12:11 +03:00			`ConditionPathExists=/dev/pts/%I`
machinectl: add new command to spawn a getty inside a container 2013-10-31 04:25:44 +04:00
units: add Conflicts=rescue.service to container-getty@.service The traditional runlevel 1 is "single user mode", and shuts down all but the main console. In systemd, rescue.target provides runlevel1.target. But it did not shut down logins on secondary consoles... if systemd was running in a container. I don't think we strictly need to change this. But when you look at both container-getty@.service and getty@.service, you see that both have IgnoreOnIsolate, but only the latter has Conflicts=rescue.service. This also makes rescue.target in a container consistent with emergency.target. In the latter case, the gettys were already stopped, because they have a Requires dependency on sysinit.target. 2017-08-07 21:24:32 +03:00			`# IgnoreOnIsolate is an issue: when someone isolates rescue.target,`
			`# tradition expects that we shut down all but the main console.`
Revert "units: don't kill the emergency shell when sysinit.target is triggered (#6765)" (#6904) This reverts commit f1e24a259ca182b6cd8a723a56da43435ce48aac. Oops. # systemctl emergency Failed to start emergency.target: Transaction order is cyclic. See syste... See system logs and 'systemctl status emergency.target' for details. # systemctl status emergency.target ● emergency.target - Emergency Mode Loaded: loaded (/usr/lib/systemd/system/emergency.target; static; vendor preset: disabled) Active: inactive (dead) since Mon 2017-09-25 10:43:02 BST; 2h 42min ago Docs: man:systemd.special(7) systemd[1]: sysinit.target: Found dependency on sysinit.target/stop sysinit.target: Unable to break cycle starting with sysinit.target/stop network.target: Found ordering cycle on wpa_supplicant.service/stop network.target: Found dependency on sysinit.target/stop network.target: Found dependency on emergency.target/start network.target: Found dependency on emergency.service/start network.target: Found dependency on serial-getty@ttyS0.service/stop network.target: Found dependency on systemd-user-sessions.service/stop network.target: Found dependency on network.target/stop network.target: Unable to break cycle starting with network.target/stop IMO #6509 is ugly enough that we should aim to answer it. But it could take some time to investigate, so let's re-open the issue as a first step. 2017-09-26 20:47:50 +03:00			`Conflicts=rescue.service`
			`Before=rescue.service`
units: add Conflicts=rescue.service to container-getty@.service The traditional runlevel 1 is "single user mode", and shuts down all but the main console. In systemd, rescue.target provides runlevel1.target. But it did not shut down logins on secondary consoles... if systemd was running in a container. I don't think we strictly need to change this. But when you look at both container-getty@.service and getty@.service, you see that both have IgnoreOnIsolate, but only the latter has Conflicts=rescue.service. This also makes rescue.target in a container consistent with emergency.target. In the latter case, the gettys were already stopped, because they have a Requires dependency on sysinit.target. 2017-08-07 21:24:32 +03:00
machinectl: add new command to spawn a getty inside a container 2013-10-31 04:25:44 +04:00			`[Service]`
units: Tell login to preserve environment (#6023) Make agetty started by getty units pass '-p' option to "login", so it doesn't clear the environment and passes whatever was setup by systemd to shells. This is needed especially for programs which are specified as user shells, but won't read locale settings from anywhere but environment. [zj: cherry-pick just the second patch from the series, see discussion on the pull request.] 2017-05-24 14:58:01 +03:00			`# The '-o' option value tells agetty to replace 'login' arguments with an`
			`# option to preserve environment (-p), followed by '--' for safety, and then`
			`# the entered username.`
			`ExecStart=-/sbin/agetty -o '-p -- \\u' --noclear --keep-baud pts/%I 115200,38400,9600 $TERM`
machinectl: add new command to spawn a getty inside a container 2013-10-31 04:25:44 +04:00			`Type=idle`
			`Restart=always`
			`RestartSec=0`
units: fix all TTY paths for container gettys Spotted by Christian Seiler: http://lists.freedesktop.org/archives/systemd-devel/2015-January/027441.html 2015-01-27 16:28:45 +03:00			`UtmpIdentifier=pts/%I`
			`TTYPath=/dev/pts/%I`
machinectl: add new command to spawn a getty inside a container 2013-10-31 04:25:44 +04:00			`TTYReset=yes`
			`TTYVHangup=yes`
			`KillMode=process`
			`IgnoreSIGPIPE=no`
			`SendSIGHUP=yes`