man: describe which units types are stopped on isolate

Fixes #6455.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek
2017-07-28 05:17:05 -04:00
parent b66c294c4b
commit 26adf7741d
2 changed files with 10 additions and 7 deletions
+5 -3
View File
@@ -819,9 +819,11 @@ Sun 2017-02-26 20:57:49 EST 2h 3min left Sun 2017-02-26 11:56:36 EST 6h ago
<term><command>isolate <replaceable>NAME</replaceable></command></term>
<listitem>
<para>Start the unit specified on the command line and its
dependencies and stop all others. If a unit name with no
extension is given, an extension of
<para>Start the unit specified on the command line and its dependencies
and stop all others, unless they have
<option>IgnoreOnIsolate=yes</option> (see
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>).
If a unit name with no extension is given, an extension of
<literal>.target</literal> will be assumed.</para>
<para>This is similar to changing the runlevel in a
+5 -4
View File
@@ -651,10 +651,11 @@
<varlistentry>
<term><varname>IgnoreOnIsolate=</varname></term>
<listitem><para>Takes a boolean argument. If
<option>true</option>, this unit will not be stopped when
isolating another unit. Defaults to
<option>false</option>.</para></listitem>
<listitem><para>Takes a boolean argument. If <option>true</option>, this unit
will not be stopped when isolating another unit. Defaults to
<option>false</option> for service, target, socket, busname, timer, and path
units, and <option>true</option> for slice, scope, device, swap, mount, and
automount units.</para></listitem>
</varlistentry>
<varlistentry>