picnoir
/
Systemd
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

man: merge two sections into two subsections of one section 

Those are very close subjects that are a good fit for one section.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2018-04-16 18:00:33 +02:00
parent 75695fb798
commit aed5cb03db
12 changed files with 343 additions and 294 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
man/systemd.automount.xml
View File

@ -76,30 +76,34 @@
</refsect1>
<refsect1>
<title>Implicit Dependencies</title>
<title>Automatic Dependencies</title>
<para>The following dependencies are implicitly added:</para>
<refsect2>
<title>Implicit Dependencies</title>
<itemizedlist>
<listitem><para>If an automount unit is beneath another mount unit in the
file system hierarchy, both a requirement and an ordering
dependency between both units are created automatically.</para></listitem>
<para>The following dependencies are implicitly added:</para>
<listitem><para>An implicit <varname>Before=</varname> dependency is created
between an automount unit and the mount unit it activates.</para></listitem>
</itemizedlist>
</refsect1>
<itemizedlist>
<listitem><para>If an automount unit is beneath another mount unit in the
file system hierarchy, both a requirement and an ordering
dependency between both units are created automatically.</para></listitem>
<refsect1>
<title>Default Dependencies</title>
<listitem><para>An implicit <varname>Before=</varname> dependency is created
between an automount unit and the mount unit it activates.</para></listitem>
</itemizedlist>
</refsect2>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<refsect2>
<title>Default Dependencies</title>
<itemizedlist>
<listitem><para>Automount units acquire automatic <varname>Before=</varname> and
<varname>Conflicts=</varname> on <filename>umount.target</filename> in order to be stopped during
shutdown.</para></listitem>
</itemizedlist>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<itemizedlist>
<listitem><para>Automount units acquire automatic <varname>Before=</varname> and
<varname>Conflicts=</varname> on <filename>umount.target</filename> in order to be stopped during
shutdown.</para></listitem>
</itemizedlist>
</refsect2>
</refsect1>
<refsect1>

29
man/systemd.device.xml
View File

@ -77,25 +77,28 @@
corresponding device generates a <literal>changed</literal> event.
Other units can use <varname>ReloadPropagatedFrom=</varname> to react
to that event</para>
</refsect1>
<refsect1>
<title>Implicit Dependencies</title>
<title>Automatic Dependencies</title>
<para>Many unit types automatically acquire dependencies on device
units of devices they require. For example,
<filename>.socket</filename> unit acquire dependencies on the
device units of the network interface specified in
<varname>BindToDevice=</varname>. Similar, swap and mount units
acquire dependencies on the units encapsulating their backing
block devices.</para>
</refsect1>
<refsect2>
<title>Implicit Dependencies</title>
<refsect1>
<title>Default Dependencies</title>
<para>Many unit types automatically acquire dependencies on device
units of devices they require. For example,
<filename>.socket</filename> unit acquire dependencies on the
device units of the network interface specified in
<varname>BindToDevice=</varname>. Similar, swap and mount units
acquire dependencies on the units encapsulating their backing
block devices.</para>
</refsect2>
<para>There are no default dependencies for device units.</para>
<refsect2>
<title>Default Dependencies</title>
<para>There are no default dependencies for device units.</para>
</refsect2>
</refsect1>
<refsect1>

84
man/systemd.mount.xml
View File

@ -102,57 +102,61 @@
</refsect1>
<refsect1>
<title>Implicit Dependencies</title>
<title>Automatic Dependencies</title>
<para>The following dependencies are implicitly added:</para>
<refsect2>
<title>Implicit Dependencies</title>
<itemizedlist>
<listitem><para>If a mount unit is beneath another mount unit in the file
system hierarchy, both a requirement dependency and an ordering
dependency between both units are created automatically.</para></listitem>
<para>The following dependencies are implicitly added:</para>
<listitem><para>Block device backed file systems automatically gain
<varname>BindsTo=</varname> and <varname>After=</varname> type
dependencies on the device unit encapsulating the block
device (see below).</para></listitem>
<itemizedlist>
<listitem><para>If a mount unit is beneath another mount unit in the file
system hierarchy, both a requirement dependency and an ordering
dependency between both units are created automatically.</para></listitem>
<listitem><para>If traditional file system quota is enabled for a mount
unit, automatic <varname>Wants=</varname> and
<varname>Before=</varname> dependencies on
<filename>systemd-quotacheck.service</filename> and
<filename>quotaon.service</filename> are added.</para></listitem>
<listitem><para>Block device backed file systems automatically gain
<varname>BindsTo=</varname> and <varname>After=</varname> type
dependencies on the device unit encapsulating the block
device (see below).</para></listitem>
<listitem><para>Additional implicit dependencies may be added as result of
execution and resource control parameters as documented in
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
and
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para></listitem>
</itemizedlist>
</refsect1>
<listitem><para>If traditional file system quota is enabled for a mount
unit, automatic <varname>Wants=</varname> and
<varname>Before=</varname> dependencies on
<filename>systemd-quotacheck.service</filename> and
<filename>quotaon.service</filename> are added.</para></listitem>
<refsect1>
<title>Default Dependencies</title>
<listitem><para>Additional implicit dependencies may be added as result of
execution and resource control parameters as documented in
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
and
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para></listitem>
</itemizedlist>
</refsect2>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<refsect2>
<title>Default Dependencies</title>
<itemizedlist>
<listitem><para>All mount units acquire automatic <varname>Before=</varname> and <varname>Conflicts=</varname> on
<filename>umount.target</filename> in order to be stopped during shutdown.</para></listitem>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<listitem><para>Mount units referring to local file systems automatically gain
an <varname>After=</varname> dependency on <filename>local-fs-pre.target</filename>.</para></listitem>
<itemizedlist>
<listitem><para>All mount units acquire automatic <varname>Before=</varname> and <varname>Conflicts=</varname> on
<filename>umount.target</filename> in order to be stopped during shutdown.</para></listitem>
<listitem><para>Network mount units
automatically acquire <varname>After=</varname> dependencies on <filename>remote-fs-pre.target</filename>,
<filename>network.target</filename> and <filename>network-online.target</filename>. Towards the latter a
<varname>Wants=</varname> unit is added as well.</para></listitem>
</itemizedlist>
<listitem><para>Mount units referring to local file systems automatically gain
an <varname>After=</varname> dependency on <filename>local-fs-pre.target</filename>.</para></listitem>
<para>Mount units referring to local and network file systems are
distinguished by their file system type specification. In some cases this is not sufficient (for example network
block device based mounts, such as iSCSI), in which case <option>_netdev</option> may be added to the mount option
string of the unit, which forces systemd to consider the mount unit a network mount.</para>
<listitem><para>Network mount units
automatically acquire <varname>After=</varname> dependencies on <filename>remote-fs-pre.target</filename>,
<filename>network.target</filename> and <filename>network-online.target</filename>. Towards the latter a
<varname>Wants=</varname> unit is added as well.</para></listitem>
</itemizedlist>
<para>Mount units referring to local and network file systems are distinguished by their file system type
specification. In some cases this is not sufficient (for example network block device based mounts, such as
iSCSI), in which case <option>_netdev</option> may be added to the mount option string of the unit, which forces
systemd to consider the mount unit a network mount.</para>
</refsect2>
</refsect1>
<refsect1>

50
man/systemd.path.xml
View File

@ -71,36 +71,40 @@
</refsect1>
<refsect1>
<title>Implicit Dependencies</title>
<title>Automatic Dependencies</title>
<para>The following dependencies are implicitly added:</para>
<refsect2>
<title>Implicit Dependencies</title>
<itemizedlist>
<listitem><para>If a path unit is beneath another mount unit in the file
system hierarchy, both a requirement and an ordering dependency
between both units are created automatically.</para></listitem>
<para>The following dependencies are implicitly added:</para>
<listitem><para>An implicit <varname>Before=</varname> dependency is added
between a path unit and the unit it is supposed to activate.</para></listitem>
</itemizedlist>
</refsect1>
<itemizedlist>
<listitem><para>If a path unit is beneath another mount unit in the file
system hierarchy, both a requirement and an ordering dependency
between both units are created automatically.</para></listitem>
<refsect1>
<title>Default Dependencies</title>
<listitem><para>An implicit <varname>Before=</varname> dependency is added
between a path unit and the unit it is supposed to activate.</para></listitem>
</itemizedlist>
</refsect2>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<refsect2>
<title>Default Dependencies</title>
<itemizedlist>
<listitem><para>Path units will automatically have dependencies of type <varname>Before=</varname> on
<filename>paths.target</filename>,
dependencies of type <varname>After=</varname> and <varname>Requires=</varname> on
<filename>sysinit.target</filename>, and have dependencies of type <varname>Conflicts=</varname> and
<varname>Before=</varname> on <filename>shutdown.target</filename>. These ensure that path units are terminated
cleanly prior to system shutdown. Only path units involved with early boot or late system shutdown should
disable <varname>DefaultDependencies=</varname> option.</para></listitem>
</itemizedlist>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<para></para>
<itemizedlist>
<listitem><para>Path units will automatically have dependencies of type <varname>Before=</varname> on
<filename>paths.target</filename>,
dependencies of type <varname>After=</varname> and <varname>Requires=</varname> on
<filename>sysinit.target</filename>, and have dependencies of type <varname>Conflicts=</varname> and
<varname>Before=</varname> on <filename>shutdown.target</filename>. These ensure that path units are terminated
cleanly prior to system shutdown. Only path units involved with early boot or late system shutdown should
disable <varname>DefaultDependencies=</varname> option.</para></listitem>
</itemizedlist>
<para></para>
</refsect2>
</refsect1>
<refsect1>

42
man/systemd.scope.xml
View File

@ -64,29 +64,33 @@
</refsect1>
<refsect1>
<title>Implicit Dependencies</title>
<title>Automatic Dependencies</title>
<para>Implicit dependencies may be added as result of
resource control parameters as documented in
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect1>
<refsect2>
<title>Implicit Dependencies</title>
<refsect1>
<title>Default Dependencies</title>
<para>Implicit dependencies may be added as result of
resource control parameters as documented in
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect2>
<para>The following dependencies are added unless
<varname>DefaultDependencies=no</varname> is set:</para>
<refsect2>
<title>Default Dependencies</title>
<itemizedlist>
<listitem><para>Scope units will automatically have dependencies of
type <varname>Conflicts=</varname> and
<varname>Before=</varname> on
<filename>shutdown.target</filename>. These ensure
that scope units are removed prior to system
shutdown. Only scope units involved with early boot or
late system shutdown should disable
<varname>DefaultDependencies=</varname> option.</para></listitem>
</itemizedlist>
<para>The following dependencies are added unless
<varname>DefaultDependencies=no</varname> is set:</para>
<itemizedlist>
<listitem><para>Scope units will automatically have dependencies of
type <varname>Conflicts=</varname> and
<varname>Before=</varname> on
<filename>shutdown.target</filename>. These ensure
that scope units are removed prior to system
shutdown. Only scope units involved with early boot or
late system shutdown should disable
<varname>DefaultDependencies=</varname> option.</para></listitem>
</itemizedlist>
</refsect2>
</refsect1>
<refsect1>

86
man/systemd.service.xml
View File

@ -92,55 +92,59 @@
</refsect1>
<refsect1>
<title>Implicit Dependencies</title>
<title>Automatic Dependencies</title>
<para>The following dependencies are implicitly added:</para>
<refsect2>
<title>Implicit Dependencies</title>
<itemizedlist>
<listitem><para>Services with <varname>Type=dbus</varname> set automatically
acquire dependencies of type <varname>Requires=</varname> and
<varname>After=</varname> on
<filename>dbus.socket</filename>.</para></listitem>
<para>The following dependencies are implicitly added:</para>
<listitem><para>Socket activated services are automatically ordered after
their activating <filename>.socket</filename> units via an
automatic <varname>After=</varname> dependency.
Services also pull in all <filename>.socket</filename> units
listed in <varname>Sockets=</varname> via automatic
<varname>Wants=</varname> and <varname>After=</varname> dependencies.</para></listitem>
</itemizedlist>
<itemizedlist>
<listitem><para>Services with <varname>Type=dbus</varname> set automatically
acquire dependencies of type <varname>Requires=</varname> and
<varname>After=</varname> on
<filename>dbus.socket</filename>.</para></listitem>
<para>Additional implicit dependencies may be added as result of
execution and resource control parameters as documented in
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
and
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect1>
<listitem><para>Socket activated services are automatically ordered after
their activating <filename>.socket</filename> units via an
automatic <varname>After=</varname> dependency.
Services also pull in all <filename>.socket</filename> units
listed in <varname>Sockets=</varname> via automatic
<varname>Wants=</varname> and <varname>After=</varname> dependencies.</para></listitem>
</itemizedlist>
<refsect1>
<title>Default Dependencies</title>
<para>Additional implicit dependencies may be added as result of
execution and resource control parameters as documented in
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
and
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect2>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<refsect2>
<title>Default Dependencies</title>
<itemizedlist>
<listitem><para>Service units will have dependencies of type <varname>Requires=</varname> and
<varname>After=</varname> on <filename>sysinit.target</filename>, a dependency of type <varname>After=</varname> on
<filename>basic.target</filename> as well as dependencies of type <varname>Conflicts=</varname> and
<varname>Before=</varname> on <filename>shutdown.target</filename>. These ensure that normal service units pull in
basic system initialization, and are terminated cleanly prior to system shutdown. Only services involved with early
boot or late system shutdown should disable this option.</para></listitem>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<listitem><para>Instanced service units (i.e. service units with an <literal>@</literal> in their name) are assigned by
default a per-template slice unit (see
<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>), named after the
template unit, containing all instances of the specific template. This slice is normally stopped at shutdown,
together with all template instances. If that is not desired, set <varname>DefaultDependencies=no</varname> in the
template unit, and either define your own per-template slice unit file that also sets
<varname>DefaultDependencies=no</varname>, or set <varname>Slice=system.slice</varname> (or another suitable slice)
in the template unit. Also see
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para></listitem>
</itemizedlist>
<itemizedlist>
<listitem><para>Service units will have dependencies of type <varname>Requires=</varname> and
<varname>After=</varname> on <filename>sysinit.target</filename>, a dependency of type <varname>After=</varname> on
<filename>basic.target</filename> as well as dependencies of type <varname>Conflicts=</varname> and
<varname>Before=</varname> on <filename>shutdown.target</filename>. These ensure that normal service units pull in
basic system initialization, and are terminated cleanly prior to system shutdown. Only services involved with early
boot or late system shutdown should disable this option.</para></listitem>
<listitem><para>Instanced service units (i.e. service units with an <literal>@</literal> in their name) are assigned by
default a per-template slice unit (see
<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>), named after the
template unit, containing all instances of the specific template. This slice is normally stopped at shutdown,
together with all template instances. If that is not desired, set <varname>DefaultDependencies=no</varname> in the
template unit, and either define your own per-template slice unit file that also sets
<varname>DefaultDependencies=no</varname>, or set <varname>Slice=system.slice</varname> (or another suitable slice)
in the template unit. Also see
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para></listitem>
</itemizedlist>
</refsect2>
</refsect1>
<refsect1>

40
man/systemd.slice.xml
View File

@ -85,29 +85,33 @@
</refsect1>
<refsect1>
<title>Implicit Dependencies</title>
<title>Automatic Dependencies</title>
<para>The following dependencies are implicitly added:</para>
<refsect2>
<title>Implicit Dependencies</title>
<itemizedlist>
<listitem><para>Slice units automatically gain dependencies of type
<varname>After=</varname> and <varname>Requires=</varname> on
their immediate parent slice unit.</para></listitem>
</itemizedlist>
</refsect1>
<para>The following dependencies are implicitly added:</para>
<refsect1>
<title>Default Dependencies</title>
<itemizedlist>
<listitem><para>Slice units automatically gain dependencies of type
<varname>After=</varname> and <varname>Requires=</varname> on
their immediate parent slice unit.</para></listitem>
</itemizedlist>
</refsect2>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<refsect2>
<title>Default Dependencies</title>
<itemizedlist>
<listitem><para>Slice units will automatically have dependencies of type <varname>Conflicts=</varname> and
<varname>Before=</varname> on
<filename>shutdown.target</filename>. These ensure that slice units are removed prior to system shutdown.
Only slice units involved with late system shutdown should disable
<varname>DefaultDependencies=</varname> option.</para></listitem>
</itemizedlist>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<itemizedlist>
<listitem><para>Slice units will automatically have dependencies of type <varname>Conflicts=</varname> and
<varname>Before=</varname> on
<filename>shutdown.target</filename>. These ensure that slice units are removed prior to system shutdown.
Only slice units involved with late system shutdown should disable
<varname>DefaultDependencies=</varname> option.</para></listitem>
</itemizedlist>
</refsect2>
</refsect1>
<refsect1>

80
man/systemd.socket.xml
View File

@ -110,53 +110,57 @@
</refsect1>
<refsect1>
<title>Implicit Dependencies</title>
<title>Automatic Dependencies</title>
<para>The following dependencies are implicitly added:</para>
<refsect2>
<title>Implicit Dependencies</title>
<itemizedlist>
<listitem><para>Socket units automatically gain a <varname>Before=</varname>
dependency on the service units they activate.</para></listitem>
<para>The following dependencies are implicitly added:</para>
<listitem><para>Socket units referring to file system paths (such as AF_UNIX
sockets or FIFOs) implicitly gain <varname>Requires=</varname> and
<varname>After=</varname> dependencies on all mount units
necessary to access those paths.</para></listitem>
<itemizedlist>
<listitem><para>Socket units automatically gain a <varname>Before=</varname>
dependency on the service units they activate.</para></listitem>
<listitem><para>Socket units using the <varname>BindToDevice=</varname>
setting automatically gain a <varname>BindsTo=</varname> and
<varname>After=</varname> dependency on the device unit
encapsulating the specified network interface.</para></listitem>
</itemizedlist>
<listitem><para>Socket units referring to file system paths (such as AF_UNIX
sockets or FIFOs) implicitly gain <varname>Requires=</varname> and
<varname>After=</varname> dependencies on all mount units
necessary to access those paths.</para></listitem>
<para>Additional implicit dependencies may be added as result of
execution and resource control parameters as documented in
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
and
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect1>
<listitem><para>Socket units using the <varname>BindToDevice=</varname>
setting automatically gain a <varname>BindsTo=</varname> and
<varname>After=</varname> dependency on the device unit
encapsulating the specified network interface.</para></listitem>
</itemizedlist>
<refsect1>
<title>Default Dependencies</title>
<para>Additional implicit dependencies may be added as result of
execution and resource control parameters as documented in
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
and
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect2>
<para>The following dependencies are added unless
<varname>DefaultDependencies=no</varname> is set:</para>
<refsect2>
<title>Default Dependencies</title>
<itemizedlist>
<listitem><para>Socket units automatically gain a
<varname>Before=</varname> dependency on
<filename>sockets.target</filename>.</para></listitem>
<para>The following dependencies are added unless
<varname>DefaultDependencies=no</varname> is set:</para>
<listitem><para>Socket units automatically gain a pair of
<varname>After=</varname> and <varname>Requires=</varname>
dependency on <filename>sysinit.target</filename>, and a pair of
<varname>Before=</varname> and <varname>Conflicts=</varname>
dependencies on <filename>shutdown.target</filename>. These
dependencies ensure that the socket unit is started before normal
services at boot, and is stopped on shutdown. Only sockets
involved with early boot or late system shutdown should disable
<varname>DefaultDependencies=</varname> option.</para></listitem>
</itemizedlist>
<itemizedlist>
<listitem><para>Socket units automatically gain a
<varname>Before=</varname> dependency on
<filename>sockets.target</filename>.</para></listitem>
<listitem><para>Socket units automatically gain a pair of
<varname>After=</varname> and <varname>Requires=</varname>
dependency on <filename>sysinit.target</filename>, and a pair of
<varname>Before=</varname> and <varname>Conflicts=</varname>
dependencies on <filename>shutdown.target</filename>. These
dependencies ensure that the socket unit is started before normal
services at boot, and is stopped on shutdown. Only sockets
involved with early boot or late system shutdown should disable
<varname>DefaultDependencies=</varname> option.</para></listitem>
</itemizedlist>
</refsect2>
</refsect1>
<refsect1>

48
man/systemd.swap.xml
View File

@ -76,34 +76,38 @@
</refsect1>
<refsect1>
<title>Implicit Dependencies</title>
<title>Automatic Dependencies</title>
<para>The following dependencies are implicitly added:</para>
<refsect2>
<title>Implicit Dependencies</title>
<itemizedlist>
<listitem><para>All swap units automatically get the
<varname>BindsTo=</varname> and <varname>After=</varname>
dependencies on the device units or the mount units of the files
they are activated from.</para></listitem>
</itemizedlist>
<para>The following dependencies are implicitly added:</para>
<para>Additional implicit dependencies may be added as result of
execution and resource control parameters as documented in
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
and
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect1>
<itemizedlist>
<listitem><para>All swap units automatically get the
<varname>BindsTo=</varname> and <varname>After=</varname>
dependencies on the device units or the mount units of the files
they are activated from.</para></listitem>
</itemizedlist>
<refsect1>
<title>Default Dependencies</title>
<para>Additional implicit dependencies may be added as result of
execution and resource control parameters as documented in
<citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
and
<citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
</refsect2>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<refsect2>
<title>Default Dependencies</title>
<itemizedlist>
<listitem><para>Swap units automatically acquire a <varname>Conflicts=</varname> and a
<varname>Before=</varname> dependency on <filename>umount.target</filename> so that they are deactivated at
shutdown as well as a <varname>Before=swap.target</varname> dependency.</para></listitem>
</itemizedlist>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<itemizedlist>
<listitem><para>Swap units automatically acquire a <varname>Conflicts=</varname> and a
<varname>Before=</varname> dependency on <filename>umount.target</filename> so that they are deactivated at
shutdown as well as a <varname>Before=swap.target</varname> dependency.</para></listitem>
</itemizedlist>
</refsect2>
</refsect1>
<refsect1>

42
man/systemd.target.xml
View File

@ -69,30 +69,34 @@
</refsect1>
<refsect1>
<title>Implicit Dependencies</title>
<title>Automatic Dependencies</title>
<para>There are no implicit dependencies for target units.</para>
</refsect1>
<refsect2>
<title>Implicit Dependencies</title>
<refsect1>
<title>Default Dependencies</title>
<para>There are no implicit dependencies for target units.</para>
</refsect2>
<para>The following dependencies are added unless
<varname>DefaultDependencies=no</varname> is set:</para>
<refsect2>
<title>Default Dependencies</title>
<itemizedlist>
<listitem><para>Target units will automatically complement all
configured dependencies of type <varname>Wants=</varname> or
<varname>Requires=</varname> with dependencies of type
<varname>After=</varname> unless <varname>DefaultDependencies=no</varname>
is set in the specified units. Note that <varname>Wants=</varname> or
<varname>Requires=</varname> must be defined in the target unit itself — if
you for example define <varname>Wants=</varname>some.target in
some.service, the automatic ordering will not be added.</para></listitem>
<para>The following dependencies are added unless
<varname>DefaultDependencies=no</varname> is set:</para>
<listitem><para>Target units automatically gain <varname>Conflicts=</varname>
dependency against <filename>shutdown.target</filename>.</para></listitem>
</itemizedlist>
<itemizedlist>
<listitem><para>Target units will automatically complement all
configured dependencies of type <varname>Wants=</varname> or
<varname>Requires=</varname> with dependencies of type
<varname>After=</varname> unless <varname>DefaultDependencies=no</varname>
is set in the specified units. Note that <varname>Wants=</varname> or
<varname>Requires=</varname> must be defined in the target unit itself — if
you for example define <varname>Wants=</varname>some.target in
some.service, the automatic ordering will not be added.</para></listitem>
<listitem><para>Target units automatically gain <varname>Conflicts=</varname>
dependency against <filename>shutdown.target</filename>.</para></listitem>
</itemizedlist>
</refsect2>
</refsect1>
<refsect1>

38
man/systemd.timer.xml
View File

@ -82,23 +82,33 @@
</refsect1>
<refsect1>
<title>Default Dependencies</title>
<title>Automatic Dependencies</title>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<refsect2>
<title>Implicit Dependencies</title>
<itemizedlist>
<listitem><para>Timer units will automatically have dependencies of type <varname>Requires=</varname> and
<varname>After=</varname> on <filename>sysinit.target</filename>, a dependency of type <varname>Before=</varname>
on <filename>timers.target</filename>, as well as <varname>Conflicts=</varname> and <varname>Before=</varname> on
<filename>shutdown.target</filename> to ensure that they are stopped cleanly prior to system shutdown. Only timer
units involved with early boot or late system shutdown should disable the
<varname>DefaultDependencies=</varname> option.</para></listitem>
<para>There are no implicit dependencies for timer units.</para>
</refsect2>
<listitem><para>Timer units
with at least one <varname>OnCalendar=</varname> directive will have an additional <varname>After=</varname>
dependency on <filename>time-sync.target</filename> to avoid being started before the system clock has been
correctly set.</para></listitem>
</itemizedlist>
<refsect2>
<title>Default Dependencies</title>
<para>The following dependencies are added unless <varname>DefaultDependencies=no</varname> is set:</para>
<itemizedlist>
<listitem><para>Timer units will automatically have dependencies of type <varname>Requires=</varname> and
<varname>After=</varname> on <filename>sysinit.target</filename>, a dependency of type <varname>Before=</varname>
on <filename>timers.target</filename>, as well as <varname>Conflicts=</varname> and <varname>Before=</varname> on
<filename>shutdown.target</filename> to ensure that they are stopped cleanly prior to system shutdown. Only timer
units involved with early boot or late system shutdown should disable the
<varname>DefaultDependencies=</varname> option.</para></listitem>
<listitem><para>Timer units
with at least one <varname>OnCalendar=</varname> directive will have an additional <varname>After=</varname>
dependency on <filename>time-sync.target</filename> to avoid being started before the system clock has been
correctly set.</para></listitem>
</itemizedlist>
</refsect2>
</refsect1>
<refsect1>

58
man/systemd.unit.xml
View File

@ -268,40 +268,40 @@
</refsect1>
<refsect1>
<title>Implicit Dependencies</title>
<title>Automatic dependencies</title>
<para>A number of unit dependencies are implicitly established,
depending on unit type and unit configuration. These implicit
dependencies can make unit configuration file cleaner. For the
implicit dependencies in each unit type, please refer to
section "Implicit Dependencies" in respective man pages.</para>
<refsect2>
<title>Implicit Dependencies</title>
<para>For example, service units with <varname>Type=dbus</varname>
automatically acquire dependencies of type <varname>Requires=</varname>
and <varname>After=</varname> on <filename>dbus.socket</filename>. See
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details.</para>
</refsect1>
<para>A number of unit dependencies are implicitly established, depending on unit type and
unit configuration. These implicit dependencies can make unit configuration file cleaner. For
the implicit dependencies in each unit type, please refer to section "Implicit Dependencies"
in respective man pages.</para>
<refsect1>
<title>Default Dependencies</title>
<para>For example, service units with <varname>Type=dbus</varname> automatically acquire
dependencies of type <varname>Requires=</varname> and <varname>After=</varname> on
<filename>dbus.socket</filename>. See
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details.</para>
</refsect2>
<para>Default dependencies are similar to implicit dependencies,
but can be turned on and off by setting
<varname>DefaultDependencies=</varname> to <varname>yes</varname>
(the default) and <varname>no</varname>, while implicit dependencies
are always in effect. See section "Default Dependencies" in respective
man pages for the effect of enabling
<varname>DefaultDependencies=</varname> in each unit types.</para>
<refsect2>
<title>Default Dependencies</title>
<para>For example, target units will complement all configured
dependencies of type <varname>Wants=</varname> or
<varname>Requires=</varname> with dependencies of type
<varname>After=</varname> unless <varname>DefaultDependencies=no</varname>
is set in the specified units. See
<citerefentry><refentrytitle>systemd.target</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details. Note that this behavior can be turned off by setting
<varname>DefaultDependencies=no</varname>.</para>
<para>Default dependencies are similar to implicit dependencies, but can be turned on and off
by setting <varname>DefaultDependencies=</varname> to <varname>yes</varname> (the default) and
<varname>no</varname>, while implicit dependencies are always in effect. See section "Default
Dependencies" in respective man pages for the effect of enabling
<varname>DefaultDependencies=</varname> in each unit types.</para>
<para>For example, target units will complement all configured dependencies of type
<varname>Wants=</varname> or <varname>Requires=</varname> with dependencies of type
<varname>After=</varname> unless <varname>DefaultDependencies=no</varname> is set in the
specified units. See
<citerefentry><refentrytitle>systemd.target</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for details. Note that this behavior can be turned off by setting
<varname>DefaultDependencies=no</varname>.</para>
</refsect2>
</refsect1>
<refsect1>