summaryrefslogtreecommitdiffstats
path: root/man/systemd-getty-generator.xml
blob: 507a001ca592e2c03ce739c657995437eddcb847 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
<?xml version="1.0"?>
<!--*-nxml-*-->
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!-- SPDX-License-Identifier: LGPL-2.1-or-later -->
<refentry id="systemd-getty-generator">

  <refentryinfo>
    <title>systemd-getty-generator</title>
    <productname>systemd</productname>
  </refentryinfo>

  <refmeta>
    <refentrytitle>systemd-getty-generator</refentrytitle>
    <manvolnum>8</manvolnum>
  </refmeta>

  <refnamediv>
    <refname>systemd-getty-generator</refname>
    <refpurpose>Generator for enabling getty instances on the
    console</refpurpose>
  </refnamediv>

  <refsynopsisdiv>
    <para><filename>/usr/lib/systemd/system-generators/systemd-getty-generator</filename></para>
  </refsynopsisdiv>

  <refsect1>
    <title>Description</title>

    <para><filename>systemd-getty-generator</filename> is a generator that automatically instantiates
    <filename>serial-getty@.service</filename> on the kernel console(s), if they can function as ttys and are
    not provided by the virtual console subsystem. It will also instantiate
    <filename>serial-getty@.service</filename> instances for virtualizer consoles, if execution in a
    virtualized environment is detected. If execution in a container environment is detected, it will instead
    enable <filename>console-getty.service</filename> for <filename>/dev/console</filename>, and
    <filename>container-getty@.service</filename> instances for additional container pseudo TTYs as requested
    by the container manager (see <ulink url="https://systemd.io/CONTAINER_INTERFACE"><filename>Container
    Interface</filename></ulink>). This should ensure that the user is shown a login prompt at the right
    place, regardless of which environment the system is started in. For example, it is sufficient to
    redirect the kernel console with a kernel command line argument such as <varname>console=</varname> to
    get both kernel messages and a getty prompt on a serial TTY. See <ulink
    url="https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt"><filename>kernel-parameters.txt</filename></ulink>
    for more information on the <varname>console=</varname> kernel parameter.</para>

    <para><filename>systemd-getty-generator</filename> implements
    <citerefentry><refentrytitle>systemd.generator</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>

    <para>Further information about configuration of gettys can be
    found in
    <ulink url="http://0pointer.de/blog/projects/serial-console.html">systemd
    for Administrators, Part XVI: Gettys on Serial Consoles (and
    Elsewhere)</ulink>.</para>
  </refsect1>

  <refsect1>
    <title>See Also</title>
    <para>
      <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
      <citerefentry project='man-pages'><refentrytitle>agetty</refentrytitle><manvolnum>8</manvolnum></citerefentry>
    </para>
  </refsect1>

</refentry>