mirror of
https://github.com/systemd/systemd-stable.git
synced 2024-12-24 21:34:08 +03:00
fdbbee37d5
Docbook styles required those to be present, even though the templates that we use did not show those names anywhere. But something changed semi-recently (I would suspect docbook templates, but there was only a minor version bump in recent years, and the changelog does not suggest anything related), and builds now work without those entries. Let's drop this dead weight. Tested with F26-F29, debian unstable. $ perl -i -0pe 's/\s*<authorgroup>.*<.authorgroup>//gms' man/*xml
72 lines
2.8 KiB
XML
72 lines
2.8 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+
|
|
-->
|
|
<refentry id="systemd-debug-generator">
|
|
|
|
<refentryinfo>
|
|
<title>systemd-debug-generator</title>
|
|
<productname>systemd</productname>
|
|
</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>
|