morgan/systemd
1
0
Fork 0
mirror of https://github.com/morgan9e/systemd synced 2026-04-15 00:47:10 +09:00
Code Issues Packages Projects Releases Wiki Activity
Files
main
systemd/units/container-getty@.service.in

48 lines
1.4 KiB
SYSTEMD
Raw Permalink Normal View History

license: LGPL-2.1+ -> LGPL-2.1-or-later
2020-11-09 13:23:58 +09:00
# SPDX-License-Identifier: LGPL-2.1-or-later
Add SPDX license headers to unit files
2017-11-18 17:35:03 +01:00
#
machinectl: add new command to spawn a getty inside a container
2013-10-31 01:25:44 +01: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 18:30:56 +01:00
Documentation=man:agetty(8) man:systemd-getty-generator(8)
Documentation=man:machinectl(1)
units: order getty units after getty-pre.target unconditionally Those two units had this ordering conditionalized on HAVE_SYSV_COMPAT. This seems strange. 45e27532971ac84e835a2879df510a581f933fcd added the ordering differently for those two files without any comment, and I think it was just pasted or scripted erroneously.
2023-05-19 15:05:30 +02:00
After=systemd-user-sessions.service plymouth-quit-wait.service getty-pre.target
meson: use jinja2 for unit templates We don't need two (and half) templating systems anymore, yay! I'm keeping the changes minimal, to make the diff manageable. Some enhancements due to a better templating system might be possible in the future. For handling of '## ' — see the next commit.
2021-05-16 11:55:36 +02:00
{% if HAVE_SYSV_COMPAT %}
units: order getty units after getty-pre.target unconditionally Those two units had this ordering conditionalized on HAVE_SYSV_COMPAT. This seems strange. 45e27532971ac84e835a2879df510a581f933fcd added the ordering differently for those two files without any comment, and I think it was just pasted or scripted erroneously.
2023-05-19 15:05:30 +02:00
After=rc-local.service
meson: use jinja2 for unit templates We don't need two (and half) templating systems anymore, yay! I'm keeping the changes minimal, to make the diff manageable. Some enhancements due to a better templating system might be possible in the future. For handling of '## ' — see the next commit.
2021-05-16 11:55:36 +02:00
{% endif %}
machinectl: add new command to spawn a getty inside a container
2013-10-31 01:25:44 +01:00
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 02:12:11 +01:00
ConditionPathExists=/dev/pts/%I
machinectl: add new command to spawn a getty inside a container
2013-10-31 01:25:44 +01: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 19:24:32 +01: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 18:47:50 +01: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 19:24:32 +01:00
machinectl: add new command to spawn a getty inside a container
2013-10-31 01:25:44 +01:00
[Service]
units/*getty*: use /usr/sbin/agetty Same way that we do it for quotaon and debug-shell by going through meson
2025-08-24 14:01:17 +02:00
ExecStart=-{{AGETTY}} --noreset --noclear --issue-file=/etc/issue:/etc/issue.d:/run/issue.d:/usr/lib/issue.d - ${TERM}
machinectl: add new command to spawn a getty inside a container
2013-10-31 01:25:44 +01: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 14:28:45 +01:00
UtmpIdentifier=pts/%I
getty: Pass tty to use by agetty via stdin If the tty arg is set to "-", agetty uses the stdin fd as the tty. Let's pass the tty this way so that we keep an fd open to the tty at all times. If all fd's to a tty are closed, the kernel might reset the tty which we want to avoid.
2021-10-29 13:54:31 +01:00
StandardInput=tty
StandardOutput=tty
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 14:28:45 +01:00
TTYPath=/dev/pts/%I
machinectl: add new command to spawn a getty inside a container
2013-10-31 01:25:44 +01:00
TTYReset=yes
TTYVHangup=yes
meson: use jinja2 for unit templates We don't need two (and half) templating systems anymore, yay! I'm keeping the changes minimal, to make the diff manageable. Some enhancements due to a better templating system might be possible in the future. For handling of '## ' — see the next commit.
2021-05-16 11:55:36 +02:00
{% if not ENABLE_LOGIND %}
machinectl: add new command to spawn a getty inside a container
2013-10-31 01:25:44 +01:00
KillMode=process
meson: use jinja2 for unit templates We don't need two (and half) templating systems anymore, yay! I'm keeping the changes minimal, to make the diff manageable. Some enhancements due to a better templating system might be possible in the future. For handling of '## ' — see the next commit.
2021-05-16 11:55:36 +02:00
{% endif %}
machinectl: add new command to spawn a getty inside a container
2013-10-31 01:25:44 +01:00
IgnoreSIGPIPE=no
SendSIGHUP=yes
units: Import tty specific credentials for each getty unit As explained in the previous commit, this allows us to configure agetty and login for individual ttys instead of globally.
2024-07-30 16:22:34 +02:00
ImportCredential=tty.container.%I.agetty.*:agetty.
ImportCredential=tty.container.%I.login.*:login.
units: Load agetty credentials in all getty units In it's latest release, agetty will support reading the agetty.autologin and login.noauth credentials, so let's make sure we import those in our getty units so they're available to agetty to read.
2023-07-27 16:50:58 +02:00
ImportCredential=agetty.*
ImportCredential=login.*
shell: define three system credentials we can propagate into shell prompts and welcome messages
2024-09-06 16:30:54 +02:00
ImportCredential=shell.*
Reference in New Issue Copy Permalink