11a1589223
Files which are installed as-is (any .service and other unit files, .conf files, .policy files, etc), are left as is. My assumption is that SPDX identifiers are not yet that well known, so it's better to retain the extended header to avoid any doubt. I also kept any copyright lines. We can probably remove them, but it'd nice to obtain explicit acks from all involved authors before doing that.
85 lines
3.1 KiB
XML
85 lines
3.1 KiB
XML
<?xml version="1.0"?>
|
|
<!--*-nxml-*-->
|
|
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
|
|
<!--
|
|
SPDX-License-Identifier: LGPL-2.1+
|
|
|
|
This file is part of systemd.
|
|
|
|
Copyright 2014 Lennart Poettering
|
|
-->
|
|
<refentry id="systemd-debug-generator">
|
|
|
|
<refentryinfo>
|
|
<title>systemd-debug-generator</title>
|
|
<productname>systemd</productname>
|
|
|
|
<authorgroup>
|
|
<author>
|
|
<contrib>Developer</contrib>
|
|
<firstname>Lennart</firstname>
|
|
<surname>Poettering</surname>
|
|
<email>lennart@poettering.net</email>
|
|
</author>
|
|
</authorgroup>
|
|
</refentryinfo>
|
|
|
|
<refmeta>
|
|
<refentrytitle>systemd-debug-generator</refentrytitle>
|
|
<manvolnum>8</manvolnum>
|
|
</refmeta>
|
|
|
|
<refnamediv>
|
|
<refname>systemd-debug-generator</refname>
|
|
<refpurpose>Generator for enabling a runtime debug shell and
|
|
masking specific units at boot</refpurpose>
|
|
</refnamediv>
|
|
|
|
<refsynopsisdiv>
|
|
<para><filename>/usr/lib/systemd/system-generators/systemd-debug-generator</filename></para>
|
|
</refsynopsisdiv>
|
|
|
|
<refsect1>
|
|
<title>Description</title>
|
|
|
|
<para><filename>systemd-debug-generator</filename> is a generator
|
|
that reads the kernel command line and understands three
|
|
options:</para>
|
|
|
|
<para>If the <option>systemd.mask=</option> option is specified
|
|
and followed by a unit name, this unit is masked for the runtime,
|
|
similar to the effect of
|
|
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
|
|
<command>mask</command> command. This is useful to boot with
|
|
certain units removed from the initial boot transaction for
|
|
debugging system startup. May be specified more than once.</para>
|
|
|
|
<para>If the <option>systemd.wants=</option> option is specified
|
|
and followed by a unit name, a start job for this unit is added to
|
|
the initial transaction. This is useful to start one or more
|
|
additional units at boot. May be specified more than once.</para>
|
|
|
|
<para>If the <option>systemd.debug_shell</option> option is
|
|
specified, the debug shell service
|
|
<literal>debug-shell.service</literal> is pulled into the boot
|
|
transaction. It will spawn a debug shell on tty9 during early
|
|
system startup. Note that the shell may also be turned on
|
|
persistently by enabling it with
|
|
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
|
|
<command>enable</command> command.</para>
|
|
|
|
<para><filename>systemd-debug-generator</filename> implements
|
|
<citerefentry><refentrytitle>systemd.generator</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
|
|
</refsect1>
|
|
|
|
<refsect1>
|
|
<title>See Also</title>
|
|
<para>
|
|
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
|
<citerefentry><refentrytitle>systemctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
|
|
<citerefentry><refentrytitle>kernel-command-line</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
|
</para>
|
|
</refsect1>
|
|
|
|
</refentry>
|