From aed5cb03db916de7e685eaf59975c41326e4f778 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Mon, 16 Apr 2018 18:00:33 +0200 Subject: man: merge two sections into two subsections of one section Those are very close subjects that are a good fit for one section. --- man/systemd.unit.xml | 68 ++++++++++++++++++++++++++-------------------------- 1 file changed, 34 insertions(+), 34 deletions(-) (limited to 'man/systemd.unit.xml') diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 9264dd1472..1519ef3e6d 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -268,40 +268,40 @@ - Implicit Dependencies - - 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. - - For example, service units with Type=dbus - automatically acquire dependencies of type Requires= - and After= on dbus.socket. See - systemd.service5 - for details. - - - - Default Dependencies - - Default dependencies are similar to implicit dependencies, - but can be turned on and off by setting - DefaultDependencies= to yes - (the default) and no, while implicit dependencies - are always in effect. See section "Default Dependencies" in respective - man pages for the effect of enabling - DefaultDependencies= in each unit types. - - For example, target units will complement all configured - dependencies of type Wants= or - Requires= with dependencies of type - After= unless DefaultDependencies=no - is set in the specified units. See - systemd.target5 - for details. Note that this behavior can be turned off by setting - DefaultDependencies=no. + Automatic dependencies + + + Implicit Dependencies + + 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. + + For example, service units with Type=dbus automatically acquire + dependencies of type Requires= and After= on + dbus.socket. See + systemd.service5 + for details. + + + + Default Dependencies + + Default dependencies are similar to implicit dependencies, but can be turned on and off + by setting DefaultDependencies= to yes (the default) and + no, while implicit dependencies are always in effect. See section "Default + Dependencies" in respective man pages for the effect of enabling + DefaultDependencies= in each unit types. + + For example, target units will complement all configured dependencies of type + Wants= or Requires= with dependencies of type + After= unless DefaultDependencies=no is set in the + specified units. See + systemd.target5 + for details. Note that this behavior can be turned off by setting + DefaultDependencies=no. + -- cgit v1.2.3