<variablelist>
<varlistentry>
- <term><option>--help</option></term>
<term><option>-h</option></term>
+ <term><option>--help</option></term>
<listitem><para>Prints a short help
text and exits.</para></listitem>
</varlistentry>
<varlistentry>
- <term><option>--type=</option></term>
<term><option>-t</option></term>
+ <term><option>--type=</option></term>
<listitem><para>The argument should
be a unit type name such as
certain unit types. If not specified
units of in all load states will be
shown.</para>
+
+ <para>As a special case, if the argument
+ is <option>help</option>, a list of
+ allowed values will be printed and the
+ program will exit.</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><option>--property=</option></term>
<term><option>-p</option></term>
+ <term><option>--property=</option></term>
<listitem><para>When showing
unit/job/manager properties, limit
</varlistentry>
<varlistentry>
- <term><option>--all</option></term>
<term><option>-a</option></term>
+ <term><option>--all</option></term>
<listitem><para>When listing units,
show all units, regardless of their
<term><option>--full</option></term>
<listitem><para>Do not ellipsize unit
- names and truncate unit descriptions
+ names, cgroup members, and truncate unit descriptions
in the output of
<command>list-units</command> and
<command>list-jobs</command>.</para></listitem>
</varlistentry>
<varlistentry>
- <term><option>--quiet</option></term>
+ <term><option>-i</option></term>
+ <term><option>--ignore-inhibitors</option></term>
+
+ <listitem><para>When system shutdown
+ or a sleep state is requested, ignore
+ inhibitor locks. Applications can
+ establish inhibitor locks to avoid
+ that certain important operations
+ (such as CD burning or suchlike) are
+ interrupted by system shutdown or a
+ sleep state. Any user may take these
+ locks and privileged users may
+ override these locks. If any locks are
+ taken, shutdown and sleep state
+ requests will normally fail
+ (regardless if privileged or not) and
+ list of active locks is
+ printed. However if
+ <option>--ignore-inhibitors</option>
+ is specified the locks are ignored and
+ not printed, and the operation
+ attempted anyway, possibly requiring
+ additional
+ privileges.</para></listitem>
+ </varlistentry>
+
+ <varlistentry>
<term><option>-q</option></term>
+ <term><option>--quiet</option></term>
<listitem><para>Suppress output to
STDOUT in
<command>snapshot</command>,
<command>is-active</command>,
+ <command>is-failed</command>,
<command>enable</command> and
<command>disable</command>.</para></listitem>
</varlistentry>
manager of the calling user.</para></listitem>
</varlistentry>
- <varlistentry>
- <term><option>--order</option></term>
- <term><option>--require</option></term>
-
- <listitem><para>When used in
- conjunction with the
- <command>dot</command> command (see
- below), selects which dependencies are
- shown in the dependency graph. If
- <option>--order</option> is passed
- only dependencies of type
- <varname>After=</varname> or
- <varname>Before=</varname> are
- shown. If <option>--require</option>
- is passed only dependencies of type
- <varname>Requires=</varname>,
- <varname>RequiresOverridable=</varname>,
- <varname>Requisite=</varname>,
- <varname>RequisiteOverridable=</varname>,
- <varname>Wants=</varname> and
- <varname>Conflicts=</varname> are
- shown. If neither is passed, shows
- dependencies of all these
- types.</para></listitem>
- </varlistentry>
-
<varlistentry>
<term><option>--no-wall</option></term>
</varlistentry>
<varlistentry>
- <term><option>--signal=</option></term>
<term><option>-s</option></term>
+ <term><option>--signal=</option></term>
<listitem><para>When used with
<command>kill</command>, choose which
</varlistentry>
<varlistentry>
- <term><option>--force</option></term>
<term><option>-f</option></term>
+ <term><option>--force</option></term>
<listitem><para>When used with
<command>enable</command>, overwrite any
</varlistentry>
<varlistentry>
- <term><option>--lines=</option></term>
<term><option>-n</option></term>
+ <term><option>--lines=</option></term>
<listitem><para>When used with
<command>status</command> controls the
</varlistentry>
<varlistentry>
- <term><option>--output=</option></term>
<term><option>-o</option></term>
+ <term><option>--output=</option></term>
<listitem><para>When used with
<command>status</command> controls the
<varlistentry>
<term><command>list-units</command></term>
- <listitem><para>List known units.</para></listitem>
+ <listitem><para>List known units (subject to limitations
+ specified with <option>-t</option>).</para>
+
+ <para>This is the default command.</para></listitem>
</varlistentry>
<varlistentry>
<term><command>start [NAME...]</command></term>
this will also print the current unit
state to STDOUT.</para></listitem>
</varlistentry>
+ <varlistentry>
+ <term><command>is-failed [NAME...]</command></term>
+
+ <listitem><para>Check whether any of
+ the specified units are failed.
+ Returns an exit code
+ 0 if at least one is failed, non-zero
+ otherwise. Unless
+ <option>--quiet</option> is specified
+ this will also print the current unit
+ state to STDOUT.</para></listitem>
+ </varlistentry>
<varlistentry>
<term><command>status [NAME...|PID...]</command></term>
<listitem><para>Show terse runtime
status information about one or more
- units, followed by its most recent log
- data from the journal. This function
- is intended to generate human-readable
- output. If you are looking for
- computer-parsable output, use
- <command>show</command> instead. If a
- PID is passed information about the
- unit the process of the PID belongs to
- is shown.</para></listitem>
+ units, followed by most recent log
+ data from the journal. If no units are
+ specified, show all units (subject to
+ limitations specified with
+ <option>-t</option>). If a PID is
+ passed show information about the unit
+ the process belongs to.</para>
+
+ <para>This function is intended to
+ generate human-readable output. If you
+ are looking for computer-parsable
+ output, use <command>show</command>
+ instead.</para></listitem>
</varlistentry>
<varlistentry>
<term><command>show [NAME...|JOB...]</command></term>
applications.</para></listitem>
</varlistentry>
<varlistentry>
- <term><command>dot</command></term>
+ <term><command>list-dependencies [NAME]</command></term>
- <listitem><para>Generate textual
- dependency graph description in dot
- format for further processing with the
- GraphViz
- <citerefentry><refentrytitle>dot</refentrytitle><manvolnum>1</manvolnum></citerefentry>
- tool. Use a command line like
- <command>systemctl dot | dot -Tsvg >
- systemd.svg</command> to generate a
- graphical dependency tree. Unless
- <option>--order</option> or
- <option>--require</option> is passed
- the generated graph will show both
- ordering and requirement
- dependencies.</para></listitem>
+ <listitem><para> Shows required and
+ wanted units of the specified unit. If
+ no unit is specified
+ <filename>default.target</filename> is
+ implied. Target units are recursively
+ expanded. When <option>--all</option>
+ is passed all other units aare
+ recursively expanded as well.</para>
+ </listitem>
</varlistentry>
<varlistentry>
<term><command>snapshot [NAME]</command></term>
<refsect1>
<title>Environment</title>
- <variablelist>
+ <variablelist class='environment-variables'>
<varlistentry>
<term><varname>$SYSTEMD_PAGER</varname></term>
<listitem><para>Pager to use when