picnoir
/
Systemd
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Systemd/units/getty@.service.m4

59 lines
2.0 KiB
Plaintext
Raw Normal View History

units: add distribution-specific units
2010-05-17 01:34:36 +02:00
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
relicense to LGPLv2.1 (with exceptions) We finally got the OK from all contributors with non-trivial commits to relicense systemd from GPL2+ to LGPL2.1+. Some udev bits continue to be GPL2+ for now, but we are looking into relicensing them too, to allow free copy/paste of all code within systemd. The bits that used to be MIT continue to be MIT. The big benefit of the relicensing is that closed source code may now link against libsystemd-login.so and friends.
2012-04-12 00:20:58 +02:00
# 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
units: add distribution-specific units
2010-05-17 01:34:36 +02:00
# (at your option) any later version.
[Unit]
Description=Getty on %I
unit: link up getty configuration from man page and unit files
2012-11-20 20:09:38 +01:00
Documentation=man:agetty(8) man:systemd-getty-generator(8)
Documentation=http://0pointer.de/blog/projects/serial-console.html
units: introduce getty-pre.target (#6667) This new target is a passive unit, hence it is supposed to be pulled in to the transaction by the service that wants to block login on the console (e.g. text version of initial-setup). Now both getty and serial-getty are ordered after this target. https://lists.freedesktop.org/archives/systemd-devel/2015-July/033754.html
2017-08-31 11:20:14 +02:00
After=systemd-user-sessions.service plymouth-quit-wait.service getty-pre.target
units: drop distro specific stuff from units Since rc-local is now enabled via the SysV compatibility we should only refer to it based on that too.
2013-01-04 22:36:48 +01:00
m4_ifdef(`HAVE_SYSV_COMPAT',
Add Mageia support This patch adds support for the Mageia Linux distribution: http://www.mageia.org/ Mageia is a fork of Mandriva although some divergence has already occured and thus inclusion of these changes upstream allow us to (hopefully) migrate more rapidly to the new standard approaches systemd offers. Indeed, we already use the preferred mechanism of OS identification via the /etc/os-release file rather than a distro specific variation. This patch mostly mirrors the patch added previously for Mandriva support. In addition to those original authors, this patch was mostly written by Dexter Morgan with help from Colin Guthrie and Eugeni Dodonov.
2011-10-28 19:16:33 +02:00
After=rc-local.service
)m4_dnl
units: add distribution-specific units
2010-05-17 01:34:36 +02:00
units: enable utmp for serial gettys too
2010-10-08 18:22:44 +02:00
# If additional gettys are spawned during boot then we should make
# sure that this is synchronized before getty.target, even though
# getty.target didn't actually pull it in.
units: make sure getty@xxx.service is always run before gettys.target
2010-08-18 23:10:27 +02:00
Before=getty.target
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.
2012-04-11 21:58:33 +02:00
IgnoreOnIsolate=yes
units: make sure getty@xxx.service is always run before gettys.target
2010-08-18 23:10:27 +02:00
getty@.service.m4: add Conflicts=/Before= against rescue.service (#3792) If user isolates rescue target from multi-user or graphical target (or just starts the service), IgnoreOnIsolate will cause issues with sulogin which is directly started on current virtual console. This patch adds necessary Conflicts= and Before= against rescue.service. Note that this is not needed for emergency target, as implicit Requires= and After= against sysinit.target is in effect for this service (DefaultDependencies=yes).
2016-07-25 16:18:00 +02:00
# IgnoreOnIsolate causes issues with sulogin, if someone isolates
# rescue.target or starts rescue.service from multi-user.target or
# graphical.target.
units: don't kill the emergency shell when sysinit.target is triggered (#6765) Why --- The advantage of this is that starting sysinit.target from the emergency shell will no longer kill the emergency shell and lock you out of the system. Our docs already claimed that emergency.target was useful for "starting individual units in order to continue the boot process in steps". This resolves #6509 for my purposes. Remaining limitation -------------------- Starting getty.target will still kill the shell, and if you don't have a root password you will then be locked out at that point. This is relevant to distributions which patch the sulogin system to permit logins when the root password is locked. Both Debian and RedHat used to follow this behaviour! Debian have been discussing what they could replace it with at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806852 So this doesn't quite achieve perfection, but I think it's a worthwhile change. It should be easier to understand the logic now it doesn't have such a big hole in it. Repairing the sysinit stage of the boot is the main reason we have emergency.target. And as discussed in the issue, sysinit.target gets pulled in implicitly as soon as any DefaultDependencies service is activated. How --- sysinit.target only needs to conflict with emergency.target. It didn't need to conflict with emergency.service as well. In theory the conflicts are pointless, we could just change the dependency of sysinit.target on local-fs.target from Wants to Requires. However, doing so would mean that when local-fs fails, the screen is flooded with yellow [DEPEND] failures. That would hinder the poor unfortunate admin, so let's not do that. There is no additional ordering requirement against emergency. If the failure happens, the job for sysinit will be cancelled instantly. We don't need to worry about when sysinit.target and its dependents would be stopped, because sysinit waits for local-fs before it starts. emergency.target is still necessarily stopped once we reach sysinit (you can't express a one-way conflict in pure unit directives). This is largely cosmetic... though perhaps it symbolizes that you're no longer in Emergency Mode if System Initialization is successful ;-). As a secondary advantage, the getty's which conflict on rescue.service now need to conflict on emergency.service as well. This makes the system more uniform and simpler to understand. The only other effect this should have is that `systemctl start emergency.target` is now practically the same as `systemctl start rescue.target`. The only units this command will stop are the conflicting getty units. Neither of those commands should ever be used. E.g. they will not stop the gdm.service unit on Fedora 26.
2017-09-14 21:43:43 +02:00
Conflicts=rescue.service emergency.service
Before=rescue.service emergency.service
getty@.service.m4: add Conflicts=/Before= against rescue.service (#3792) If user isolates rescue target from multi-user or graphical target (or just starts the service), IgnoreOnIsolate will cause issues with sulogin which is directly started on current virtual console. This patch adds necessary Conflicts= and Before= against rescue.service. Note that this is not needed for emergency target, as implicit Requires= and After= against sysinit.target is in effect for this service (DefaultDependencies=yes).
2016-07-25 16:18:00 +02:00
units: do not special-case getty@tty1.service installation Since a long while we can use "systemctl enable getty@tty1.service" which does the right thing, so there's no need to abuse Alias= for installation.
2013-07-13 15:59:35 +02:00
# On systems without virtual consoles, don't start any getty. Note
getty: skip VC gettys if the VC subsystem is not available
2012-04-12 17:31:26 +02:00
# that serial gettys are covered by serial-getty@.service, not this
units: do not special-case getty@tty1.service installation Since a long while we can use "systemctl enable getty@tty1.service" which does the right thing, so there's no need to abuse Alias= for installation.
2013-07-13 15:59:35 +02:00
# unit.
getty: skip VC gettys if the VC subsystem is not available
2012-04-12 17:31:26 +02:00
ConditionPathExists=/dev/tty0
units: add distribution-specific units
2010-05-17 01:34:36 +02:00
[Service]
units: avoid redundant VT clearing by agetty TTYVTDisallocate=yes already clears the VT. agetty does not need to do it again. Run it with --noclear. Felix Miata found the double clearing confusing in this bugreport: https://bugzilla.redhat.com/show_bug.cgi?id=828007 Add a comment explaining what clears the VT.
2012-06-06 11:26:30 +02:00
# the VT is cleared by TTYVTDisallocate
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 13:58:01 +02: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 %I $TERM
service: introduce Type=idle and use it for gettys Type=idle is much like Type=simple, however between the fork() and the exec() in the child we wait until PID 1 informs us that no jobs are left. This is mostly a cosmetic fix to make gettys appear only after all boot output is finished and complete. Note that this does not impact the normal job logic as we do not delay the completion of any jobs. We just delay the invocation of the actual binary, and only for services that otherwise would be of Type=simple.
2012-04-24 14:28:00 +02:00
Type=idle
service: rename settings for Restart= from 'restart-always' to 'always' and similar
2010-10-05 20:30:44 +02:00
Restart=always
units: fix execution environment for a few services
2010-05-18 03:08:18 +02:00
RestartSec=0
service: optionally, create INIT_PROCESS/DEAD_PROCESS entries for a service This should fix accounting for pam_limits and suchlike. https://bugzilla.redhat.com/show_bug.cgi?id=636036
2010-10-08 16:06:23 +02:00
UtmpIdentifier=%I
exec: hangup/reset/deallocate VTs in gettys Explicitly disconnect all clients from a VT when a getty starts/finishes (requires TIOCVHANGUP, available in 2.6.29). Explicitly deallocate getty VTs in order to flush scrollback buffer. Explicitly reset terminals to a defined state before spawning getty.
2011-05-18 01:07:31 +02:00
TTYPath=/dev/%I
TTYReset=yes
TTYVHangup=yes
TTYVTDisallocate=yes
exec: drop process group kill mode since it has little use and confuses the user
2011-03-29 23:31:38 +02:00
KillMode=process
service: ignore SIGPIPE by default
2012-02-09 03:18:04 +01:00
IgnoreSIGPIPE=no
core: optionally send SIGHUP in addition to the configured kill signal This is useful to fake session ends for processes like shells.
2013-07-30 01:54:59 +02:00
SendSIGHUP=yes
units: always send HUP when dealing with shells/gettys/logins
2010-08-05 20:29:11 +02:00
getty: unset locale before execution On the console indian characters cannot be displayed, hence it is advisable to disable indian locales on the console, which most distributions traditionally did from a shell fragment executed post login. If getty gets started with locale settings passed it would itself however be translated without the no-indian-on-console fixup applied. Hence, for now don't pass any locale settings to getty/login, and thus rely on the classic post-login script fragment to set and fix the locale. Eventually we probably want to drop this again since the system locale should be read and set at one place, and not at multiple, and that one place should be PID 1. https://bugzilla.redhat.com/show_bug.cgi?id=663900
2011-01-06 20:38:06 +01:00
# Unset locale for the console getty since the console has problems
# displaying some internationalized messages.
units: properly unset the l10n environment variables where we need to Now that we have UnsetEnvironment=, let's make proper use of it for unsetting l10n settings for console gettys. Fixes: #6407
2017-09-10 12:19:02 +02:00
UnsetEnvironment=LANG LANGUAGE LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT LC_IDENTIFICATION
getty: unset locale before execution On the console indian characters cannot be displayed, hence it is advisable to disable indian locales on the console, which most distributions traditionally did from a shell fragment executed post login. If getty gets started with locale settings passed it would itself however be translated without the no-indian-on-console fixup applied. Hence, for now don't pass any locale settings to getty/login, and thus rely on the classic post-login script fragment to set and fix the locale. Eventually we probably want to drop this again since the system locale should be read and set at one place, and not at multiple, and that one place should be PID 1. https://bugzilla.redhat.com/show_bug.cgi?id=663900
2011-01-06 20:38:06 +01:00
unit: add [Install] section to various service files
2010-06-18 21:56:21 +02:00
[Install]
units: do not special-case getty@tty1.service installation Since a long while we can use "systemctl enable getty@tty1.service" which does the right thing, so there's no need to abuse Alias= for installation.
2013-07-13 15:59:35 +02:00
WantedBy=getty.target
install: introduce new DefaultInstance= field for [Install] sections The DefaultInstance= name is used when enabling template units when only specifying the template name, but no instance. Add DefaultInstance=tty1 to getty@.service, so that when the template itself is enabled an instance for tty1 is created. This is useful so that we "systemctl preset-all" can work properly, because we can operate on getty@.service after finding it, and the right instance is created.
2014-06-17 00:15:31 +02:00
DefaultInstance=tty1