mirror of
https://github.com/systemd/systemd-stable.git
synced 2024-10-27 10:25:06 +03:00
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't
This also adds a short explanation paragraph for this.
This commit is contained in:
Lennart Poettering
parent
627506f104
commit
54f874c56b
4
TODO
4
TODO
@ -51,10 +51,6 @@ Features:
|
||||
|
||||
* when prompting for a hdd password show GUID partition label
|
||||
|
||||
* document which targets shall be pulled in by users of the facility,
|
||||
and which ones are to be pulled in by the implementors of the
|
||||
facility.
|
||||
|
||||
* teach udev + logind's uaccess to somehow handle the "dead" device nodes from:
|
||||
/lib/modules/$(uname -r)/modules.devname
|
||||
and apply ACLs to them if they have TAG=="uaccess" in udev rules.
|
||||
|
||||
@ -138,22 +138,6 @@
|
||||
daemons.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>bluetooth.target</filename></term>
|
||||
<listitem>
|
||||
<para>This target is started
|
||||
automatically as soon as a
|
||||
Bluetooth controller is
|
||||
plugged in or becomes
|
||||
available at boot.</para>
|
||||
|
||||
<para>This may be used to pull
|
||||
in Bluetooth management
|
||||
daemons dynamically when
|
||||
Bluetooth hardware is
|
||||
found.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>ctrl-alt-del.target</filename></term>
|
||||
<listitem>
|
||||
@ -381,18 +365,6 @@
|
||||
option set.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>local-fs-pre.target</filename></term>
|
||||
<listitem>
|
||||
<para>This target unit is
|
||||
automatically ordered before
|
||||
all local mount points marked
|
||||
with <option>auto</option>
|
||||
(see above). It can be used to
|
||||
execute certain units before
|
||||
all local mounts.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>multi-user.target</filename></term>
|
||||
<listitem>
|
||||
@ -438,42 +410,6 @@
|
||||
information.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>nss-lookup.target</filename></term>
|
||||
<listitem>
|
||||
<para>A target that should be
|
||||
used as synchronization point
|
||||
for all host/network name
|
||||
service lookups. Note that
|
||||
this is independent of
|
||||
user/group name lookups for
|
||||
which
|
||||
<filename>nss-user-lookup.target</filename>
|
||||
should be used. systemd
|
||||
automatically adds
|
||||
dependencies of type
|
||||
<varname>After=</varname> for
|
||||
this target unit to all SysV
|
||||
init script service units with
|
||||
an LSB header referring to the
|
||||
<literal>$named</literal>
|
||||
facility.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>nss-user-lookup.target</filename></term>
|
||||
<listitem>
|
||||
<para>A target that should be
|
||||
used as synchronization point
|
||||
for all user/group name
|
||||
service lookups. Note that
|
||||
this is independent of
|
||||
host/network name lookups for
|
||||
which
|
||||
<filename>nss-lookup.target</filename>
|
||||
should be used. </para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>paths.target</filename></term>
|
||||
<listitem>
|
||||
@ -512,22 +448,6 @@
|
||||
unit, for compatibility with SysV.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>printer.target</filename></term>
|
||||
<listitem>
|
||||
<para>This target is started
|
||||
automatically as soon as a
|
||||
printer is plugged in or
|
||||
becomes available at
|
||||
boot.</para>
|
||||
|
||||
<para>This may be used to pull
|
||||
in printer management
|
||||
daemons dynamically when
|
||||
printer hardware is
|
||||
found.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>reboot.target</filename></term>
|
||||
<listitem>
|
||||
@ -561,36 +481,6 @@
|
||||
facility.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>remote-fs-pre.target</filename></term>
|
||||
<listitem>
|
||||
<para>This target unit is
|
||||
automatically ordered before
|
||||
all remote mount point units
|
||||
(see above). It can be used to
|
||||
run certain units before the
|
||||
remote mounts are
|
||||
established. Note that this
|
||||
unit is generally not part of
|
||||
the initial transaction,
|
||||
unless the unit that wants to
|
||||
be ordered before all remote
|
||||
mounts pulls it in via a
|
||||
<varname>Wants=</varname> type
|
||||
dependency. If the unit wants
|
||||
to be pulled in by the first
|
||||
remote mount showing up it
|
||||
should use
|
||||
<filename>remote-fs-setup.target</filename>
|
||||
(see below).</para>
|
||||
|
||||
<para>Again, this target unit
|
||||
is <emphasis>not</emphasis>
|
||||
suitable for pulling in other
|
||||
units, it is only useful for
|
||||
ordering.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>remote-fs-setup.target</filename></term>
|
||||
<listitem>
|
||||
@ -605,7 +495,7 @@
|
||||
this target is not ordered
|
||||
against the remote mounts, use
|
||||
<filename>remote-fs-pre.target</filename>
|
||||
for that.</para>
|
||||
for that (see below).</para>
|
||||
|
||||
<para>Again, this target unit
|
||||
is <emphasis>not</emphasis>
|
||||
@ -640,19 +530,6 @@
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>rpcbind.target</filename></term>
|
||||
<listitem>
|
||||
<para>systemd automatically
|
||||
adds dependencies of type
|
||||
<varname>After=</varname> for
|
||||
this target unit to all SysV
|
||||
init script service units with
|
||||
an LSB header referring to the
|
||||
<literal>$portmap</literal>
|
||||
facility.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>runlevel2.target</filename></term>
|
||||
<term><filename>runlevel3.target</filename></term>
|
||||
@ -714,22 +591,6 @@
|
||||
logic.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>smartcard.target</filename></term>
|
||||
<listitem>
|
||||
<para>This target is started
|
||||
automatically as soon as a
|
||||
smartcard controller is
|
||||
plugged in or becomes
|
||||
available at boot.</para>
|
||||
|
||||
<para>This may be used to pull
|
||||
in printer management
|
||||
daemons dynamically when
|
||||
smartcard hardware is
|
||||
found.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>sockets.target</filename></term>
|
||||
<listitem>
|
||||
@ -753,21 +614,6 @@
|
||||
section.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>sound.target</filename></term>
|
||||
<listitem>
|
||||
<para>This target is started
|
||||
automatically as soon as a
|
||||
sound card is plugged in or
|
||||
becomes available at
|
||||
boot.</para>
|
||||
|
||||
<para>This may be used to pull
|
||||
in audio management daemons
|
||||
dynamically when printer
|
||||
hardware is found.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>suspend.target</filename></term>
|
||||
<listitem>
|
||||
@ -826,19 +672,6 @@
|
||||
Specification</ulink>.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>time-sync.target</filename></term>
|
||||
<listitem>
|
||||
<para>systemd automatically
|
||||
adds dependencies of type
|
||||
<varname>After=</varname> for
|
||||
this target unit to all SysV
|
||||
init script service units with
|
||||
an LSB header referring to the
|
||||
<literal>$time</literal>
|
||||
facility.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>timers.target</filename></term>
|
||||
<listitem>
|
||||
@ -884,6 +717,208 @@
|
||||
</variablelist>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Special System Units for Devices</title>
|
||||
|
||||
<para>Some target units are automatically pulled in as
|
||||
devices of certain kinds show up in the system. These
|
||||
may be used to automatically activate various services
|
||||
based on the specific type of the available
|
||||
hardware.</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><filename>bluetooth.target</filename></term>
|
||||
<listitem>
|
||||
<para>This target is started
|
||||
automatically as soon as a
|
||||
Bluetooth controller is
|
||||
plugged in or becomes
|
||||
available at boot.</para>
|
||||
|
||||
<para>This may be used to pull
|
||||
in Bluetooth management
|
||||
daemons dynamically when
|
||||
Bluetooth hardware is
|
||||
found.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>printer.target</filename></term>
|
||||
<listitem>
|
||||
<para>This target is started
|
||||
automatically as soon as a
|
||||
printer is plugged in or
|
||||
becomes available at
|
||||
boot.</para>
|
||||
|
||||
<para>This may be used to pull
|
||||
in printer management
|
||||
daemons dynamically when
|
||||
printer hardware is
|
||||
found.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>smartcard.target</filename></term>
|
||||
<listitem>
|
||||
<para>This target is started
|
||||
automatically as soon as a
|
||||
smartcard controller is
|
||||
plugged in or becomes
|
||||
available at boot.</para>
|
||||
|
||||
<para>This may be used to pull
|
||||
in printer management
|
||||
daemons dynamically when
|
||||
smartcard hardware is
|
||||
found.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>sound.target</filename></term>
|
||||
<listitem>
|
||||
<para>This target is started
|
||||
automatically as soon as a
|
||||
sound card is plugged in or
|
||||
becomes available at
|
||||
boot.</para>
|
||||
|
||||
<para>This may be used to pull
|
||||
in audio management daemons
|
||||
dynamically when printer
|
||||
hardware is found.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Special Passive System Units </title>
|
||||
|
||||
<para>A number of special system targets are defined
|
||||
that can be used to properly order boot-up of optional
|
||||
services. These targets are generally not part of the
|
||||
initial boot transaction, unless they are explicitly
|
||||
pulled in by one of the implementing services. Note
|
||||
specifically, that these <emphasis>passive</emphasis>
|
||||
target units are generally not pulled in by the
|
||||
consumer of a service, but by the provider of the
|
||||
service. This means: a consuming service should order
|
||||
itself after these targets (as appropriate), but not
|
||||
pull it in. A providing service should order itself
|
||||
before these targets (as appropriate) and pull it in
|
||||
(via a <varname>Wants=</varname> type
|
||||
dependency).</para>
|
||||
|
||||
<variablelist>
|
||||
<varlistentry>
|
||||
<term><filename>local-fs-pre.target</filename></term>
|
||||
<listitem>
|
||||
<para>This target unit is
|
||||
automatically ordered before
|
||||
all local mount points marked
|
||||
with <option>auto</option>
|
||||
(see above). It can be used to
|
||||
execute certain units before
|
||||
all local mounts.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>nss-lookup.target</filename></term>
|
||||
<listitem>
|
||||
<para>A target that should be
|
||||
used as synchronization point
|
||||
for all host/network name
|
||||
service lookups. Note that
|
||||
this is independent of
|
||||
user/group name lookups for
|
||||
which
|
||||
<filename>nss-user-lookup.target</filename>
|
||||
should be used. systemd
|
||||
automatically adds
|
||||
dependencies of type
|
||||
<varname>After=</varname> for
|
||||
this target unit to all SysV
|
||||
init script service units with
|
||||
an LSB header referring to the
|
||||
<literal>$named</literal>
|
||||
facility.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>nss-user-lookup.target</filename></term>
|
||||
<listitem>
|
||||
<para>A target that should be
|
||||
used as synchronization point
|
||||
for all user/group name
|
||||
service lookups. Note that
|
||||
this is independent of
|
||||
host/network name lookups for
|
||||
which
|
||||
<filename>nss-lookup.target</filename>
|
||||
should be used. </para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>remote-fs-pre.target</filename></term>
|
||||
<listitem>
|
||||
<para>This target unit is
|
||||
automatically ordered before
|
||||
all remote mount point units
|
||||
(see above). It can be used to
|
||||
run certain units before the
|
||||
remote mounts are
|
||||
established. Note that this
|
||||
unit is generally not part of
|
||||
the initial transaction,
|
||||
unless the unit that wants to
|
||||
be ordered before all remote
|
||||
mounts pulls it in via a
|
||||
<varname>Wants=</varname> type
|
||||
dependency. If the unit wants
|
||||
to be pulled in by the first
|
||||
remote mount showing up it
|
||||
should use
|
||||
<filename>remote-fs-setup.target</filename>
|
||||
(see above).</para>
|
||||
|
||||
<para>Again, this target unit
|
||||
is <emphasis>not</emphasis>
|
||||
suitable for pulling in other
|
||||
units, it is only useful for
|
||||
ordering.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>rpcbind.target</filename></term>
|
||||
<listitem>
|
||||
<para>systemd automatically
|
||||
adds dependencies of type
|
||||
<varname>After=</varname> for
|
||||
this target unit to all SysV
|
||||
init script service units with
|
||||
an LSB header referring to the
|
||||
<literal>$portmap</literal>
|
||||
facility.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
<varlistentry>
|
||||
<term><filename>time-sync.target</filename></term>
|
||||
<listitem>
|
||||
<para>systemd automatically
|
||||
adds dependencies of type
|
||||
<varname>After=</varname> for
|
||||
this target unit to all SysV
|
||||
init script service units with
|
||||
an LSB header referring to the
|
||||
<literal>$time</literal>
|
||||
facility.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
</refsect1>
|
||||
|
||||
<refsect1>
|
||||
<title>Special User Units</title>
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user