From: John Lin <johnlinp@gmail.com>
Date: Tue, 12 Sep 2017 02:09:45 +0000 (+0800)
Subject: man: move bus-based/socket-based activation out of Automatic Dependencies section
X-Git-Tag: v235~104^2~1
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=bbe0b4a8d5e84ac28689ba4b6f817524375622c3;p=thirdparty%2Fsystemd.git

man: move bus-based/socket-based activation out of Automatic Dependencies section

Fixes: #6793
---

diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml
index d1819aa0ed7..32399ef9933 100644
--- a/man/systemd.unit.xml
+++ b/man/systemd.unit.xml
@@ -209,6 +209,12 @@
     <!-- Note that we do not document .include here, as we consider it mostly obsolete, and want
          people to use .d/ drop-ins instead. -->
 
+    <para>Note that while systemd offers a flexible dependency system
+    between units it is recommended to use this functionality only
+    sparingly and instead rely on techniques such as bus-based or
+    socket-based activation which make dependencies implicit,
+    resulting in a both simpler and more flexible system.</para>
+
     <para>Some unit names reflect paths existing in the file system
     namespace. Example: a device unit
     <filename>dev-sda.device</filename> refers to a device with the
@@ -264,12 +270,6 @@
   <refsect1>
     <title>Automatic Dependencies</title>
 
-    <para>Note that while systemd offers a flexible dependency system
-    between units it is recommended to use this functionality only
-    sparingly and instead rely on techniques such as bus-based or
-    socket-based activation which make dependencies implicit,
-    resulting in a both simpler and more flexible system.</para>
-
     <para>A number of unit dependencies are automatically established,
     depending on unit configuration. On top of that, for units with
     <varname>DefaultDependencies=yes</varname> (the default) a couple