man: drop recommendation to use absolute paths in ExecStart*=

The only reason to recommend this would be if people had multiple commands
with the same name in the search path. This probably was never the best idea,
and it happens rarely anyway. Since the patch that dropped requirement for full
paths was introduced, we have dropped support for unmerged-usr and we're planning
to drop support for split-bin at some point too. Many people effectively have just
one directory in the search path, so there is even less reason to use an absolute
path. So let's recommend just using the command name, which makes the unit file
shorter and nicer to read.

diff --git a/man/systemd.service.xml b/man/systemd.service.xml
index 123f1db30de8586fa2882941ece6eef7d820407f..b43ec14c375b2e7adc08e2ab9b09365d6c4dd00b 100644 (file)
--- a/man/systemd.service.xml
+++ b/man/systemd.service.xml
@@ -1421,9 +1421,9 @@
     systems using split <filename>/usr/bin/</filename> and <filename>/bin/</filename> directories, and their
     <filename>sbin/</filename> counterparts on systems using split <filename>bin/</filename> and
     <filename>sbin/</filename>. It is thus safe to use just the executable name in case of executables
-    located in any of the "standard" directories, and an absolute path must be used in other cases. Using an
-    absolute path is recommended to avoid ambiguity. Hint: this search path may be queried using
-    <command>systemd-path search-binaries-default</command>.</para>
+    located in any of the "standard" directories, and an absolute path must be used in other cases.
+    Hint: this search path may be queried using <command>systemd-path search-binaries-default</command>.
+    </para>
 
     <para>The command line accepts <literal>%</literal> specifiers as described in
     <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>