mirror of
https://github.com/Dasharo/systemd.git
synced 2026-03-06 15:02:31 -08:00
man: add missing parts to man pages
This commit is contained in:
Lennart Poettering
478
man/daemon.xml
478
man/daemon.xml
File diff suppressed because it is too large
Load Diff
@@ -64,9 +64,11 @@
|
||||
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
||||
for the common options of all unit configuration
|
||||
files. The common configuration items are configured
|
||||
in the generic [Unit] and [Install] sections. A
|
||||
separate [Device] section does not exist, since no
|
||||
device-specific options may be configured.</para>
|
||||
in the generic <literal>[Unit]</literal> and
|
||||
<literal>[Install]</literal> sections. A separate
|
||||
<literal>[Device]</literal> section does not exist,
|
||||
since no device-specific options may be
|
||||
configured.</para>
|
||||
|
||||
<para>systemd will automatically create dynamic device
|
||||
units for all kernel devices that are marked with the
|
||||
@@ -100,9 +102,15 @@
|
||||
<listitem><para>Adds dependencies of
|
||||
type <varname>Wants</varname> from
|
||||
this unit to all listed units. This
|
||||
may be used to activate arbitrary units,
|
||||
when a specific device becomes
|
||||
available.</para></listitem>
|
||||
may be used to activate arbitrary
|
||||
units, when a specific device becomes
|
||||
available. Note that this and the
|
||||
other tags are not taken into account
|
||||
unless the device is tagged with the
|
||||
"<literal>systemd</literal>" string in
|
||||
the udev database, because otherwise
|
||||
the device is not exposed as systemd
|
||||
unit.</para></listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
|
||||
106
man/systemd.xml
106
man/systemd.xml
@@ -196,6 +196,112 @@
|
||||
</variablelist>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Concepts</title>
|
||||
|
||||
<para>systemd provides a dependency system between
|
||||
various entities called "units". Units encapsulate
|
||||
various objects that are relevant for system boot-up
|
||||
and maintainance. The majority of units are configured
|
||||
in unit configuration files, whose syntax and basic
|
||||
set of options is described in
|
||||
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
|
||||
however some are created automatically from other
|
||||
configuration or dynamically from system state. Units
|
||||
may be active (meaning started, bound, plugged in, ...
|
||||
depending on the unit type), or inactive (meaning
|
||||
stopped, unbound, unplugged, ...), as well is in the
|
||||
process of being activated or deactivated,
|
||||
i.e. between the two states. The following unit types
|
||||
are available:</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem><para>Service units, which control
|
||||
daemons and the processes they consist of. For
|
||||
details see
|
||||
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
|
||||
|
||||
<listitem><para>Socket units, which
|
||||
encapsulate local IPC or network sockets in
|
||||
the system, useful for socket-based
|
||||
activation. For details about socket units see
|
||||
<citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
|
||||
for details on socket-based activation and
|
||||
other forms of activation, see
|
||||
<citerefentry><refentrytitle>daemon</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para></listitem>
|
||||
|
||||
<listitem><para>Target units are useful to
|
||||
group units, or provide well-known
|
||||
synchronization points during boot-up, see
|
||||
<citerefentry><refentrytitle>systemd.target</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
|
||||
|
||||
<listitem><para>Device units expose kernel
|
||||
devices in systemd and may be used to
|
||||
implement device-based activation. For details
|
||||
see
|
||||
<citerefentry><refentrytitle>systemd.device</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
|
||||
|
||||
<listitem><para>Mount units control mount
|
||||
points in the file system, for details see
|
||||
<citerefentry><refentrytitle>systemd.mount</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
|
||||
|
||||
<listitem><para>Automount units provide
|
||||
automount capabilities, for on-demand mounting
|
||||
of file systems as well as parallelized
|
||||
boot-up. See
|
||||
<citerefentry><refentrytitle>systemd.automount</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
|
||||
|
||||
<listitem><para>Snapshot units can be used to
|
||||
temporarily save the state of the set of
|
||||
systemd units, which later may be restored by
|
||||
activating the saved snapshot unit. For more
|
||||
information see
|
||||
<citerefentry><refentrytitle>systemd.automount</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
|
||||
|
||||
<listitem><para>Timer units are useful for
|
||||
triggering activation of other units based on
|
||||
timers. You may find details in
|
||||
<citerefentry><refentrytitle>systemd.timer</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
|
||||
|
||||
<listitem><para>Swap units are very similar to
|
||||
mount units and encapsulated memory swap
|
||||
partitions or files of the operating
|
||||
systemd. They are described in <citerefentry><refentrytitle>systemd.swap</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
|
||||
|
||||
<listitem><para>Path units may be used
|
||||
activate other services when file system
|
||||
objects change or are modified. See
|
||||
<citerefentry><refentrytitle>systemd.path</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para></listitem>
|
||||
|
||||
</orderedlist>
|
||||
|
||||
<para>Units are named as their configuration
|
||||
files. Some units have special semantics. A detailed
|
||||
list you may find in
|
||||
<citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
|
||||
|
||||
<para>On boot systemd activates the target unit
|
||||
<filename>default.target</filename> whose job it is to
|
||||
activate on-boot services and other on-boot units by
|
||||
pulling them in via dependencies. Usually the unit
|
||||
name is just an alias (symlink) for either
|
||||
<filename>graphical.target</filename> (for
|
||||
fully-featured boots into the UI) or
|
||||
<filename>multi-user.target</filename> (for limited
|
||||
console-only boots for use in embedded or server
|
||||
environments, or similar; a subset of
|
||||
graphical.target). However it is at the discretion of
|
||||
the administrator to configure it as an alias to any
|
||||
other target unit. See
|
||||
<citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>
|
||||
for details about these target units.</para>
|
||||
|
||||
<para>For more information about the concepts and
|
||||
ideas behind systemd please refer to the <ulink
|
||||
url="http://0pointer.de/blog/projects/systemd.html">Original
|
||||
Announcement Document</ulink>.</para>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Directories</title>
|
||||
|
||||
|
||||
Reference in New Issue
Block a user