<!-- Note that we don't document force-reload here, as that is just compatibility support, and we generally
don't document that. -->
- <xi:include href="version-info.xml" xpointer="v229"/>
+ <xi:include href="version-info.xml" xpointer="v229"/>
</listitem>
</varlistentry>
<varlistentry>
</tgroup>
</table>
- <xi:include href="version-info.xml" xpointer="v238"/>
-
+ <xi:include href="version-info.xml" xpointer="v238"/>
</listitem>
</varlistentry>
<command>enable</command>.</para>
<xi:include href="version-info.xml" xpointer="v217"/>
-
</listitem>
</varlistentry>
</tgroup>
</table>
- <xi:include href="version-info.xml" xpointer="v215"/>
+ <xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
<option>-P</option> once will also affect all properties listed with
<option>-p</option>/<option>--property=</option>.</para>
- <xi:include href="version-info.xml" xpointer="v246"/>
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<para>When printing properties with <command>show</command>, only print the value, and skip the
property name and <literal>=</literal>. Also see option <option>-P</option> above.</para>
- <xi:include href="version-info.xml" xpointer="v230"/>
+ <xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
<listitem>
<para>When showing sockets, show the type of the socket.</para>
- <xi:include href="version-info.xml" xpointer="v202"/>
+ <xi:include href="version-info.xml" xpointer="v202"/>
</listitem>
</varlistentry>
<term><option>--job-mode=</option></term>
<listitem>
- <para>When queuing a new job, this option controls how to deal with
- already queued jobs. It takes one of <literal>fail</literal>,
- <literal>replace</literal>,
- <literal>replace-irreversibly</literal>,
- <literal>isolate</literal>,
- <literal>ignore-dependencies</literal>,
- <literal>ignore-requirements</literal>,
- <literal>flush</literal>,
- <literal>triggering</literal>, or
- <literal>restart-dependencies</literal>. Defaults to
- <literal>replace</literal>, except when the
- <command>isolate</command> command is used which implies the
- <literal>isolate</literal> job mode.</para>
-
- <para>If <literal>fail</literal> is specified and a requested
- operation conflicts with a pending job (more specifically:
- causes an already pending start job to be reversed into a stop
- job or vice versa), cause the operation to fail.</para>
-
- <para>If <literal>replace</literal> (the default) is
- specified, any conflicting pending job will be replaced, as
- necessary.</para>
-
- <para>If <literal>replace-irreversibly</literal> is specified,
- operate like <literal>replace</literal>, but also mark the new
- jobs as irreversible. This prevents future conflicting
- transactions from replacing these jobs (or even being enqueued
- while the irreversible jobs are still pending). Irreversible
- jobs can still be cancelled using the <command>cancel</command>
- command. This job mode should be used on any transaction which
- pulls in <filename>shutdown.target</filename>.</para>
-
- <para><literal>isolate</literal> is only valid for start
- operations and causes all other units to be stopped when the
- specified unit is started. This mode is always used when the
- <command>isolate</command> command is used.</para>
-
- <para><literal>flush</literal> will cause all queued jobs to
- be canceled when the new job is enqueued.</para>
-
- <para>If <literal>ignore-dependencies</literal> is specified,
- then all unit dependencies are ignored for this new job and
- the operation is executed immediately. If passed, no required
- units of the unit passed will be pulled in, and no ordering
- dependencies will be honored. This is mostly a debugging and
- rescue tool for the administrator and should not be used by
- applications.</para>
-
- <para><literal>ignore-requirements</literal> is similar to
- <literal>ignore-dependencies</literal>, but only causes the
- requirement dependencies to be ignored, the ordering
- dependencies will still be honored.</para>
-
- <para><literal>triggering</literal> may only be used with
- <command>systemctl stop</command>. In this mode, the specified
- unit and any active units that trigger it are stopped. See the
- discussion of
- <varname>Triggers=</varname> in <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
- for more information about triggering units.</para>
-
- <para><literal>restart-dependencies</literal> may only be used with
- <command>systemctl start</command>. In this mode, dependencies of
- the specified unit will receive restart propagation, as if a restart
- job had been enqueued for the unit.</para>
-
- <xi:include href="version-info.xml" xpointer="v209"/>
+
<para>When queuing a new job, this option controls how to deal with
+ already queued jobs. It takes one of <literal>fail</literal>,
+ <literal>replace</literal>,
+ <literal>replace-irreversibly</literal>,
+ <literal>isolate</literal>,
+ <literal>ignore-dependencies</literal>,
+ <literal>ignore-requirements</literal>,
+ <literal>flush</literal>,
+ <literal>triggering</literal>, or
+ <literal>restart-dependencies</literal>. Defaults to
+ <literal>replace</literal>, except when the
+ <command>isolate</command> command is used which implies the
+ <literal>isolate</literal> job mode.</para>
+
+
<para>If <literal>fail</literal> is specified and a requested
+ operation conflicts with a pending job (more specifically:
+ causes an already pending start job to be reversed into a stop
+ job or vice versa), cause the operation to fail.</para>
+
+
<para>If <literal>replace</literal> (the default) is
+ specified, any conflicting pending job will be replaced, as
+ necessary.</para>
+
+
<para>If <literal>replace-irreversibly</literal> is specified,
+ operate like <literal>replace</literal>, but also mark the new
+ jobs as irreversible. This prevents future conflicting
+ transactions from replacing these jobs (or even being enqueued
+ while the irreversible jobs are still pending). Irreversible
+ jobs can still be cancelled using the <command>cancel</command>
+ command. This job mode should be used on any transaction which
+ pulls in <filename>shutdown.target</filename>.</para>
+
+
<para><literal>isolate</literal> is only valid for start
+ operations and causes all other units to be stopped when the
+ specified unit is started. This mode is always used when the
+ <command>isolate</command> command is used.</para>
+
+
<para><literal>flush</literal> will cause all queued jobs to
+ be canceled when the new job is enqueued.</para>
+
+
<para>If <literal>ignore-dependencies</literal> is specified,
+ then all unit dependencies are ignored for this new job and
+ the operation is executed immediately. If passed, no required
+ units of the unit passed will be pulled in, and no ordering
+ dependencies will be honored. This is mostly a debugging and
+ rescue tool for the administrator and should not be used by
+ applications.</para>
+
+
<para><literal>ignore-requirements</literal> is similar to
+ <literal>ignore-dependencies</literal>, but only causes the
+ requirement dependencies to be ignored, the ordering
+ dependencies will still be honored.</para>
+
+
<para><literal>triggering</literal> may only be used with
+ <command>systemctl stop</command>. In this mode, the specified
+ unit and any active units that trigger it are stopped. See the
+ discussion of
+ <varname>Triggers=</varname> in <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
+ for more information about triggering units.</para>
+
+
<para><literal>restart-dependencies</literal> may only be used with
+ <command>systemctl start</command>. In this mode, dependencies of
+ the specified unit will receive restart propagation, as if a restart
+ job had been enqueued for the unit.</para>
+
+ <xi:include href="version-info.xml" xpointer="v209"/>
</listitem>
</varlistentry>
run as effect of the enqueued jobs might request further jobs to be pulled in. This means that
completion of the listed jobs might ultimately entail more jobs than the listed ones.</para>
- <xi:include href="version-info.xml" xpointer="v242"/>
+ <xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
<listitem>
<para>Shortcut for <option>--check-inhibitors=no</option>.</para>
- <xi:include href="version-info.xml" xpointer="v198"/>
+ <xi:include href="version-info.xml" xpointer="v198"/>
</listitem>
</varlistentry>
<filename>&UMOUNT_PATH;</filename>), but no main process is defined. If omitted, defaults to
<option>all</option>.</para>
- <xi:include href="version-info.xml" xpointer="v252"/>
+ <xi:include href="version-info.xml" xpointer="v252"/>
</listitem>
</varlistentry>
<varname>FileDescriptorStorePreserve=</varname> option is enabled, since the file descriptor store
is otherwise cleaned automatically when the unit is stopped.</para>
- <xi:include href="version-info.xml" xpointer="v243"/>
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
short message explaining the reason for the operation. The message will be logged together with the default
shutdown message.</para>
- <xi:include href="version-info.xml" xpointer="v225"/>
+ <xi:include href="version-info.xml" xpointer="v225"/>
</listitem>
</varlistentry>
or stop operation is only carried out when the respective enable or
disable operation has been successful.</para>
- <xi:include href="version-info.xml" xpointer="v220"/>
+ <xi:include href="version-info.xml" xpointer="v220"/>
</listitem>
</varlistentry>
enabled according to the preset rules, or only enabled, or
only disabled.</para>
- <xi:include href="version-info.xml" xpointer="v215"/>
+ <xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
reboot into the firmware setup interface. Note that this functionality is not available on all
systems.</para>
- <xi:include href="version-info.xml" xpointer="v220"/>
+ <xi:include href="version-info.xml" xpointer="v220"/>
</listitem>
</varlistentry>
menu timeout. Pass zero in order to disable the menu timeout. Note that not all boot loaders
support this functionality.</para>
- <xi:include href="version-info.xml" xpointer="v242"/>
+ <xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
as argument, or <literal>help</literal> in order to list available entries. Note that not all boot
loaders support this functionality.</para>
- <xi:include href="version-info.xml" xpointer="v242"/>
+ <xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
<term><option>--reboot-argument=</option></term>
<listitem>
- <para>This switch is used with <command>reboot</command>. The value is architecture and firmware specific. As an example, <literal>recovery</literal>
- might be used to trigger system recovery, and <literal>fota</literal> might be used to trigger a
- <quote>firmware over the air</quote> update.</para>
+ <para>This switch is used with <command>reboot</command>. The value is architecture and firmware
+ specific. As an example, <literal>recovery</literal> might be used to trigger system recovery, and
+ <literal>fota</literal> might be used to trigger a <quote>firmware over the air</quote>
+ update.</para>
- <xi:include href="version-info.xml" xpointer="v246"/>
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
the output is printed as a list instead of a tree, and the bullet
circles are omitted.</para>
- <xi:include href="version-info.xml" xpointer="v203"/>
+ <xi:include href="version-info.xml" xpointer="v203"/>
</listitem>
</varlistentry>
</varlistentry>
</variablelist>
- <xi:include href="version-info.xml" xpointer="v247"/>
+ <xi:include href="version-info.xml" xpointer="v247"/>
</listitem>
</varlistentry>
section "PARSING TIMESTAMPS". Specially, if <literal>show</literal> is given, the currently scheduled
action will be shown, which can be canceled by passing an empty string or <literal>cancel</literal>.</para>
- <xi:include href="version-info.xml" xpointer="v254"/>
+ <xi:include href="version-info.xml" xpointer="v254"/>
</listitem>
</varlistentry>
projects / thirdparty / systemd.git / blobdiff