<term><option>--all</option></term>
<listitem>
- <para>When listing units, show all units, regardless of
- their state, including inactive units. When showing
+ <para>When listing units, show all loaded units, regardless
+ of their state, including inactive units. When showing
unit/job/manager properties, show all properties regardless
whether they are set or not.</para>
+ <para>To list all units installed on the system, use the
+ <command>list-unit-files</command> command instead.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--reverse</option></term>
+
+ <listitem>
+ <para>Show reverse dependencies between units with
+ <command>list-dependencies</command>, i.e. units with
+ dependencies of type <varname>Wants=</varname> or
+ <varname>Requires=</varname> on the given unit.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><option>--after</option></term>
+ <term><option>--before</option></term>
+
+ <listitem>
+ <para>Show which units are started after, resp. before
+ with <command>list-dependencies</command>.
+ </para>
</listitem>
</varlistentry>
unit name, plus a control group specification in the syntax
<replaceable>CONTROLLER</replaceable>:<replaceable>PATH</replaceable>
or <replaceable>CONTROLLER</replaceable>. In the latter syntax
- (where the path is ommitted) the default unit control group
+ (where the path is omitted) the default unit control group
path is implied. Examples: <literal>cpu</literal> or
<literal>cpu:/foo/bar</literal>. If a unit is removed from a
control group hierarchy all its processes will be moved to the