HALF ECHO LEARN / REFERENCE COLLECTION

v262.2

man/systemd.xml

80,075 bytesGit mode 100644Download original fileLGPL-2.1-or-later

Git blob: 51ce1854fbbe54d674fd526e5c21e4dd889e429d

Lines 1001–1585 of 1,585

      </varlistentry>
 
      <varlistentry>
        <term><varname>quiet</varname></term>
 
        <listitem><para>Turn off status output at boot, much like
        <varname>systemd.show_status=no</varname> would. Note that
        this option is also read by the kernel itself and disables
        kernel log output. Passing this option hence turns off the
        usual output from both the system manager and the kernel.
        </para>
 
        <xi:include href="version-info.xml" xpointer="v186"/></listitem>
      </varlistentry>
 
      <varlistentry>
        <term><varname>debug</varname></term>
 
        <listitem><para>Turn on debugging output. This is equivalent
        to <varname>systemd.log_level=debug</varname>. Note that this
        option is also read by the kernel itself and enables kernel
        debug output. Passing this option hence turns on the debug
        output from both the system manager and the
        kernel.</para>
 
        <xi:include href="version-info.xml" xpointer="v205"/></listitem>
      </varlistentry>
 
      <varlistentry>
        <term><varname>emergency</varname></term>
        <term><varname>rd.emergency</varname></term>
 
        <listitem><para>Boot into emergency mode. Those options are equivalent to
        <varname>systemd.unit=emergency.target</varname> or
        <varname>rd.systemd.unit=emergency.target</varname>, respectively. They were initially
        provided for compatibility with SysV, but are retained as convenient shortcuts.</para>
 
        <xi:include href="version-info.xml" xpointer="v186"/></listitem>
      </varlistentry>
 
      <varlistentry>
        <term><varname>rescue</varname></term>
        <term><varname>rd.rescue</varname></term>
        <term><varname>single</varname></term>
        <term><varname>1</varname></term>
 
        <listitem><para>Boot into rescue mode. Those options are equivalent to either
        <varname>systemd.unit=rescue.target</varname> or <varname>rd.systemd.unit=rescue.target</varname>.
        They were initially provided for compatibility with SysV, but are retained as convenient
        shortcuts.</para>
 
        <xi:include href="version-info.xml" xpointer="v186"/></listitem>
      </varlistentry>
 
      <varlistentry>
        <term><varname>3</varname></term>
        <term><varname>5</varname></term>
 
        <listitem><para>Shortcuts to boot into specific targets: <varname>3</varname> is equivalent to
        <varname>systemd.unit=multi-user.target</varname> and <varname>5</varname> is equivalent to
        <varname>systemd.unit=graphical.target</varname>. Those options were initially provided for
        compatibility with SysV, but are retained as convenient shortcuts.</para>
 
        <xi:include href="version-info.xml" xpointer="v186"/></listitem>
      </varlistentry>
 
      <varlistentry>
        <term><varname>locale.LANG=</varname></term>
        <term><varname>locale.LANGUAGE=</varname></term>
        <term><varname>locale.LC_CTYPE=</varname></term>
        <term><varname>locale.LC_NUMERIC=</varname></term>
        <term><varname>locale.LC_TIME=</varname></term>
        <term><varname>locale.LC_COLLATE=</varname></term>
        <term><varname>locale.LC_MONETARY=</varname></term>
        <term><varname>locale.LC_MESSAGES=</varname></term>
        <term><varname>locale.LC_PAPER=</varname></term>
        <term><varname>locale.LC_NAME=</varname></term>
        <term><varname>locale.LC_ADDRESS=</varname></term>
        <term><varname>locale.LC_TELEPHONE=</varname></term>
        <term><varname>locale.LC_MEASUREMENT=</varname></term>
        <term><varname>locale.LC_IDENTIFICATION=</varname></term>
 
        <listitem><para>Set the system locale to use. This overrides
        the settings in <filename>/etc/locale.conf</filename>. For
        more information, see
        <citerefentry project='man-pages'><refentrytitle>locale.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>
        and
        <citerefentry project='man-pages'><refentrytitle>locale</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
        </para>
 
        <xi:include href="version-info.xml" xpointer="v186"/></listitem>
      </varlistentry>
 
      <varlistentry>
        <term><varname>systemd.minimum_uptime_sec=</varname></term>
 
        <listitem><para>Takes a time in seconds. Specifies the minimum uptime of the system before the system
        shuts down. For more information see the <varname>MinimumUptimeSec=</varname> setting described in
        <citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
 
        <xi:include href="version-info.xml" xpointer="v261"/></listitem>
      </varlistentry>
    </variablelist>
 
    <para>For other kernel command line parameters understood by
    components of the core OS, please refer to
    <citerefentry><refentrytitle>kernel-command-line</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
  </refsect1>
 
  <refsect1>
    <title>System Credentials</title>
 
    <para>During initialization the service manager will import credentials from various sources into the
    system's set of credentials, which can then be propagated into services and consumed by
    generators:</para>
 
    <itemizedlist>
      <listitem><para>When the service manager first initializes it will read system credentials from SMBIOS
      Type 11 vendor strings
      <varname>io.systemd.credential:<replaceable>name</replaceable>=<replaceable>value</replaceable></varname>,
      and
      <varname>io.systemd.credential.binary:<replaceable>name</replaceable>=<replaceable>value</replaceable></varname>.</para></listitem>
 
      <listitem><para>At the same time it will import credentials from QEMU <literal>fw_cfg</literal>. (Note
      that the SMBIOS mechanism is generally preferred, because it is faster and generic.)</para></listitem>
 
      <listitem><para>Credentials may be passed via the kernel command line, using the
      <varname>systemd.set-credential=</varname> parameter, see above.</para></listitem>
 
      <listitem><para>Credentials may be passed from the UEFI environment via
      <citerefentry><refentrytitle>systemd-stub</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para></listitem>
 
      <listitem><para>When the service manager is invoked during the initrd → host transition it will import
      all files in <filename>/run/credentials/@initrd/</filename> as system credentials.</para></listitem>
    </itemizedlist>
 
    <para>Invoke
    <citerefentry><refentrytitle>systemd-creds</refentrytitle><manvolnum>1</manvolnum></citerefentry> as
    follows to see the list of credentials passed into the system:</para>
 
    <programlisting># systemd-creds --system list</programlisting>
 
    <para>For further information see <ulink url="https://systemd.io/CREDENTIALS">System and Service
    Credentials</ulink> documentation.</para>
 
    <para>The service manager when run as PID 1 consumes the following system credentials:</para>
 
    <variablelist class='system-credentials'>
      <varlistentry>
        <term><varname>vmm.notify_socket</varname></term>
        <listitem>
          <para>Contains a <constant>AF_VSOCK</constant> or <constant>AF_UNIX</constant> address where to
          send a <constant>READY=1</constant> notification message when the service manager has completed
          booting. See
          <citerefentry><refentrytitle>sd_notify</refentrytitle><manvolnum>3</manvolnum></citerefentry> and
          the next section for more information. Note that in case the hypervisor does not support
          <constant>SOCK_DGRAM</constant> over <constant>AF_VSOCK</constant>,
          <constant>SOCK_SEQPACKET</constant> will be tried instead. The credential payload for
          <constant>AF_VSOCK</constant> should be a string in the form
          <literal>vsock:CID:PORT</literal>. <literal>vsock-stream</literal>, <literal>vsock-dgram</literal>
          and <literal>vsock-seqpacket</literal> can be used instead of <literal>vsock</literal> to force
          usage of the corresponding socket type.</para>
 
          <para>This feature is useful for machine managers or other processes on the host to receive a
          notification via VSOCK when a virtual machine has finished booting.</para>
 
          <xi:include href="version-info.xml" xpointer="v254"/>
        </listitem>
      </varlistentry>
 
      <varlistentry>
        <term><varname>system.machine_id</varname></term>
        <listitem>
          <para>Takes a 128bit hexadecimal ID to initialize <filename>/etc/machine-id</filename> from, if the
          file is not set up yet. See
          <citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
          details.</para>
 
        <xi:include href="version-info.xml" xpointer="v254"/>
        </listitem>
      </varlistentry>
    </variablelist>
 
    <para>For a list of system credentials various other components of systemd consume, see
    <citerefentry><refentrytitle>systemd.system-credentials</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
  </refsect1>
 
  <refsect1>
    <title>Readiness Protocol</title>
 
    <para>The service manager implements a readiness notification protocol both between the manager and its
    services (i.e. down the stack), and between the manager and a potential supervisor further up the stack
    (the latter could be a machine or container manager, or in case of a per-user service manager the system
    service manager instance). The basic protocol (and the suggested API for it) is described in
    <citerefentry><refentrytitle>sd_notify</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para>
 
    <para>The notification socket the service manager (including PID 1) uses for reporting readiness to its
    own supervisor is set via the usual <varname>$NOTIFY_SOCKET</varname> environment variable (see
    above). Since this is directly settable only for container managers and for the per-user instance of the
    service manager, an additional mechanism to configure this is available, in particular intended for use
    in VM environments: the <varname>vmm.notify_socket</varname> system credential (see above) may be set to
    a suitable socket (typically an <constant>AF_VSOCK</constant> one) via SMBIOS Type 11 vendor strings. For
    details see above.</para>
 
    <para>The notification protocol from the service manager up the stack towards a supervisor supports a
    number of extension fields that allow a supervisor to learn about specific properties of the system and
    track its boot progress. Specifically the following fields are sent:</para>
 
    <itemizedlist>
      <listitem><para>An <varname>X_SYSTEMD_HOSTNAME=…</varname> message will be sent out once the initial
      hostname for the system has been determined. Note that during later runtime the hostname might be
      changed again programmatically, and (currently) no further notifications are sent out in that case.</para>
 
      <xi:include href="version-info.xml" xpointer="v256"/></listitem>
 
      <listitem><para>An <varname>X_SYSTEMD_MACHINE_ID=…</varname> message will be sent out once the machine
      ID of the system has been determined. See
      <citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry> for
      details.</para>
 
      <xi:include href="version-info.xml" xpointer="v256"/></listitem>
 
      <listitem><para>An <varname>X_SYSTEMD_SIGNALS_LEVEL=…</varname> message will be sent out once the
      service manager installed the various UNIX process signal handlers described above. The field's value
      is an unsigned integer formatted as decimal string, and indicates the supported UNIX process signal
      feature level of the service manager. Currently, only a single feature level is defined:</para>
 
      <itemizedlist>
        <listitem><para><varname>X_SYSTEMD_SIGNALS_LEVEL=2</varname> covers the various UNIX process signals
        documented above – which are a superset of those supported by the historical SysV init
        system.</para></listitem>
      </itemizedlist>
 
      <para>Signals sent to PID 1 before this message is sent might not be handled correctly yet. A consumer
      of these messages should parse the value as an unsigned integer that indicates the level of support.
      For now only the mentioned level 2 is defined, but later on additional levels might be defined with
      higher integers, that will implement a superset of the currently defined behaviour.</para>
 
      <xi:include href="version-info.xml" xpointer="v256"/></listitem>
 
      <listitem><para><varname>X_SYSTEMD_UNIT_ACTIVE=…</varname> and
      <varname>X_SYSTEMD_UNIT_INACTIVE=…</varname> messages will be sent out for each target unit as it
      becomes active or stops being active. This is useful to track boot progress and functionality. For
      example, once the <filename>ssh-access.target</filename> unit is reported started SSH access is
      typically available, see
      <citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry> for
      details.</para>
 
      <xi:include href="version-info.xml" xpointer="v256"/></listitem>
 
      <listitem><para>An <varname>X_SYSTEMD_SHUTDOWN=…</varname> message will be sent out very shortly before
      the system shuts down. The value is one of the strings <literal>reboot</literal>,
      <literal>halt</literal>, <literal>poweroff</literal>, <literal>kexec</literal> and indicates which kind
      of shutdown is being executed.</para>
 
      <xi:include href="version-info.xml" xpointer="v256"/></listitem>
 
      <listitem><para>An <varname>X_SYSTEMD_REBOOT_PARAMETER=…</varname> message will also be sent out very
      shortly before the system shuts down. Its value is the reboot argument as configured with
      <command>systemctl --reboot-argument=…</command>.</para>
 
      <xi:include href="version-info.xml" xpointer="v256"/></listitem>
    </itemizedlist>
 
    <para>Note that these extension fields are sent in addition to the regular <literal>READY=1</literal> and
    <literal>RELOADING=1</literal> notifications.</para>
  </refsect1>
 
  <refsect1>
    <title>Options</title>
 
    <para><command>systemd</command> is only very rarely invoked directly, since it is started early and is
    already running by the time users may interact with it. Normally, tools like
    <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry> are used to
    give commands to the manager. Since <command>systemd</command> is usually not invoked directly, the
    options listed below are mostly useful for debugging and special purposes.</para>
 
    <refsect2>
      <title>Introspection and debugging options</title>
 
      <para>Those options are used for testing and introspection, and <command>systemd</command> may
      be invoked with them at any time:</para>
 
      <variablelist>
        <varlistentry>
          <term><option>--dump-configuration-items</option></term>
 
          <listitem><para>Dump understood unit configuration items. This outputs a terse but complete list of
          configuration items understood in unit definition files.</para></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--dump-bus-properties</option></term>
 
          <listitem><para>Dump exposed bus properties. This outputs a terse but complete list of properties
          exposed on D-Bus.</para>
 
          <xi:include href="version-info.xml" xpointer="v239"/></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--test</option></term>
 
          <listitem><para>Determine the initial start-up transaction (i.e. the list of jobs enqueued at
          start-up), dump it and exit — without actually executing any of the determined jobs. This option is
          useful for debugging only. Note that during regular service manager start-up additional units not
          shown by this operation may be started, because hardware, socket, bus or other kinds of activation
          might add additional jobs as the transaction is executed. Use <option>--system</option> to request
          the initial transaction of the system service manager (this is also the implied default), combine
          with <option>--user</option> to request the initial transaction of the per-user service manager
          instead.</para></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--system</option></term>
          <term><option>--user</option></term>
 
          <listitem><para>When used in conjunction with <option>--test</option>, selects whether to calculate
          the initial transaction for the system instance or for a per-user instance. These options have no
          effect when invoked without <option>--test</option>, as during regular
          (i.e. non-<option>--test</option>) invocations the service manager will automatically detect
          whether it shall operate in system or per-user mode, by checking whether the PID it is run as is 1
          or not. Note that it is not supported booting and maintaining a system with the service manager
          running in <option>--system</option> mode but with a PID other than 1.</para></listitem>
        </varlistentry>
 
        <xi:include href="standard-options.xml" xpointer="help" />
        <xi:include href="standard-options.xml" xpointer="version" />
      </variablelist>
    </refsect2>
 
    <refsect2>
      <title>Options that duplicate kernel command line settings</title>
 
      <para>Those options correspond directly to options listed above in "Kernel Command Line". Both forms
      may be used equivalently for the system manager, but it is recommended to use the forms listed above in
      this context, because they are properly namespaced. When an option is specified both on the kernel
      command line and as a normal command line argument, the latter has higher precedence.</para>
 
      <para>When <command>systemd</command> is used as a user manager, the kernel command line is ignored and
      only the options described below are understood. Nevertheless, <command>systemd</command> is usually
      started in this mode through the
      <citerefentry><refentrytitle>user@.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
      service, which is shared between all users. It may be more convenient to use configuration files to
      modify settings (see
      <citerefentry><refentrytitle>systemd-user.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>),
      or environment variables. See the "Environment" section above for a discussion of how the environment
      block is set.</para>
 
      <variablelist>
        <varlistentry>
          <term><option>--unit=</option></term>
 
          <listitem><para>Set default unit to activate on startup. If not specified, defaults to
          <filename>default.target</filename>. See <varname>systemd.unit=</varname> above.</para></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--dump-core</option></term>
 
          <listitem><para>Enable core dumping on crash. This switch has no effect when running as user
          instance. Same as <varname>systemd.dump_core=</varname> above.</para></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--crash-vt=<replaceable>VT</replaceable></option></term>
 
          <listitem><para>Switch to a specific virtual console (VT) on crash. This switch has no effect when
          running as user instance. Same as <varname>systemd.crash_chvt=</varname> above (but not the
          different spelling!).</para>
 
          <xi:include href="version-info.xml" xpointer="v227"/></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--crash-shell</option></term>
 
          <listitem><para>Run a shell on crash. This switch has no effect when running as user instance. See
          <varname>systemd.crash_shell=</varname> above.</para></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--crash-action=</option></term>
 
          <listitem><para>Specify what to do when the system manager (PID 1) crashes. This switch has no
          effect when <command>systemd</command> is running as user instance. See
          <varname>systemd.crash_action=</varname> above.</para>
 
          <xi:include href="version-info.xml" xpointer="v256"/></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--confirm-spawn</option></term>
 
          <listitem><para>Ask for confirmation when spawning processes. This switch has no effect when run as
          user instance. See <varname>systemd.confirm_spawn</varname> above.</para></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--show-status</option></term>
 
          <listitem><para>Show terse unit status information on the console during boot-up and shutdown. See
          <varname>systemd.show_status</varname> above.</para>
 
          <xi:include href="version-info.xml" xpointer="v244"/></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--log-color</option></term>
 
          <listitem><para>Highlight important log messages. See <varname>systemd.log_color</varname> above.
          </para>
 
          <xi:include href="version-info.xml" xpointer="v244"/></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--log-level=</option></term>
 
          <listitem><para>Set log level. See <varname>systemd.log_level</varname> above.</para></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--log-location</option></term>
 
          <listitem><para>Include code location in log messages. See <varname>systemd.log_location</varname>
          above.</para>
 
          <xi:include href="version-info.xml" xpointer="v244"/></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--log-target=</option></term>
 
          <listitem><para>Set log target. See <varname>systemd.log_target</varname> above.</para></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--log-time=</option></term>
 
          <listitem><para>Prefix console messages with timestamp. See <varname>systemd.log_time</varname> above.
          </para>
 
          <xi:include href="version-info.xml" xpointer="v246"/></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--machine-id=</option></term>
 
          <listitem><para>Override the machine-id set on the hard drive. See
          <varname>systemd.machine_id=</varname> above.</para>
 
          <xi:include href="version-info.xml" xpointer="v229"/></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--service-watchdogs</option></term>
 
          <listitem><para>Globally enable/disable all service watchdog timeouts and emergency actions. See
          <varname>systemd.service_watchdogs</varname> above.</para>
 
          <xi:include href="version-info.xml" xpointer="v237"/></listitem>
        </varlistentry>
 
        <varlistentry>
          <term><option>--default-standard-output=</option></term>
          <term><option>--default-standard-error=</option></term>
 
          <listitem><para>Sets the default output or error output for all services and sockets,
          respectively. See <varname>systemd.default_standard_output=</varname> and
          <varname>systemd.default_standard_error=</varname> above.</para></listitem>
        </varlistentry>
      </variablelist>
    </refsect2>
  </refsect1>
 
  <refsect1>
    <title>System clock epoch</title>
 
    <para>When <command>systemd</command> is started or restarted, it may set the system clock to the
    "epoch". This mechanism is used to ensure that the system clock remains somewhat reasonably initialized
    and roughly monotonic across reboots, in case no battery-backed local RTC is available or it does not
    work correctly.</para>
 
    <para>The epoch is the lowest date above which the system clock time is assumed to be set correctly. When
    initializing, the local clock is <emphasis>advanced</emphasis> to the epoch if it was set to a lower
    value. As a special case, if the local clock is sufficiently far in the future (by default 15 years, but
    this can be configured at build time), the hardware clock is assumed to be broken, and the system clock
    is <emphasis>rewound</emphasis> to the epoch.</para>
 
    <para>The epoch is set to the highest of: the build time of <filename>systemd</filename>, the
    modification time ("mtime") of <filename>/usr/lib/clock-epoch</filename>, and the modification time of
    <filename>/var/lib/systemd/timesync/clock</filename>.</para>
  </refsect1>
 
  <refsect1>
    <title>Files</title>
 
    <variablelist>
      <varlistentry>
        <term><filename>/run/systemd/notify</filename></term>
 
        <listitem><para>Daemon status notification socket. This is an
        <constant>AF_UNIX</constant> datagram socket and is used to
        implement the daemon notification logic as implemented by
        <citerefentry><refentrytitle>sd_notify</refentrytitle><manvolnum>3</manvolnum></citerefentry>.</para></listitem>
 
      </varlistentry>
 
      <varlistentry>
        <term><filename>/run/systemd/private</filename></term>
 
        <listitem><para>Used internally as communication channel
        between
        <citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
        and the systemd process. This is an
        <constant>AF_UNIX</constant> stream socket. This interface is
        private to systemd and should not be used in external
        projects.</para></listitem>
      </varlistentry>
 
      <varlistentry>
        <term><filename>/usr/lib/clock-epoch</filename></term>
 
        <listitem><para>The modification time ("mtime") of this file is used for the time epoch, see previous
        section.</para>
 
        <xi:include href="version-info.xml" xpointer="v247"/></listitem>
      </varlistentry>
 
      <varlistentry>
        <term><filename>/var/lib/systemd/timesync/clock</filename></term>
 
        <listitem><para>The modification time ("mtime") of this file is updated by
        <citerefentry><refentrytitle>systemd-timesyncd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
        If present, the modification time of file is used for the epoch, see previous section.
        </para>
 
        <xi:include href="version-info.xml" xpointer="v257"/></listitem>
      </varlistentry>
    </variablelist>
  </refsect1>
 
  <refsect1>
      <title>History</title>
 
      <variablelist>
        <varlistentry>
          <term>systemd 252</term>
 
          <listitem><para>Kernel command-line arguments <varname>systemd.unified_cgroup_hierarchy</varname>
          and <varname>systemd.legacy_systemd_cgroup_controller</varname> were deprecated. Please switch to
          the unified cgroup hierarchy.</para></listitem>
        </varlistentry>
      </variablelist>
  </refsect1>
 
  <refsect1>
    <title>See Also</title>
    <para><simplelist type="inline">
      <member>The <ulink url="https://systemd.io/">systemd Homepage</ulink></member>
      <member><citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
      <member><citerefentry project='man-pages'><refentrytitle>locale.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>systemd-notify</refentrytitle><manvolnum>1</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>daemon</refentrytitle><manvolnum>7</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>sd-daemon</refentrytitle><manvolnum>3</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>org.freedesktop.systemd1</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry></member>
      <member><citerefentry project='die-net'><refentrytitle>pkg-config</refentrytitle><manvolnum>1</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>kernel-command-line</refentrytitle><manvolnum>7</manvolnum></citerefentry></member>
      <member><citerefentry project='man-pages'><refentrytitle>bootup</refentrytitle><manvolnum>7</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>systemd.directives</refentrytitle><manvolnum>7</manvolnum></citerefentry></member>
      <member><citerefentry><refentrytitle>org.freedesktop.systemd1</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
    </simplelist></para>
 
    <para>For more information about the concepts and
    ideas behind systemd, please refer to the
    <ulink url="https://0pointer.de/blog/projects/systemd.html">Original Design Document</ulink>.</para>
  </refsect1>
 
</refentry>