mirror of
https://git.proxmox.com/git/systemd
synced 2025-08-03 11:56:29 +00:00
527 lines
60 KiB
HTML
527 lines
60 KiB
HTML
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>systemctl</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><style>
|
|
a.headerlink {
|
|
color: #c60f0f;
|
|
font-size: 0.8em;
|
|
padding: 0 4px 0 4px;
|
|
text-decoration: none;
|
|
visibility: hidden;
|
|
}
|
|
|
|
a.headerlink:hover {
|
|
background-color: #c60f0f;
|
|
color: white;
|
|
}
|
|
|
|
h1:hover > a.headerlink, h2:hover > a.headerlink, h3:hover > a.headerlink, dt:hover > a.headerlink {
|
|
visibility: visible;
|
|
}
|
|
</style><a href="index.html">Index </a>·
|
|
<a href="systemd.directives.html">Directives </a>·
|
|
<a href="../python-systemd/index.html">Python </a>·
|
|
<a href="../libudev/index.html">libudev </a>·
|
|
<a href="../libudev/index.html">gudev </a><span style="float:right">systemd 204</span><hr><div class="refentry"><a name="systemctl"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>systemctl — Control the systemd system and service manager</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">systemctl</code> [OPTIONS...] COMMAND [NAME...]</p></div></div><div class="refsect1"><a name="idm259765356752"></a><h2 id="Description">Description<a class="headerlink" title="Permalink to this headline" href="#Description">¶</a></h2><p><span class="command"><strong>systemctl</strong></span> may be used to
|
|
introspect and control the state of the
|
|
<a href="systemd.html"><span class="citerefentry"><span class="refentrytitle">systemd</span>(1)</span></a>
|
|
system and service manager.</p></div><div class="refsect1"><a name="idm259765354160"></a><h2 id="Options">Options<a class="headerlink" title="Permalink to this headline" href="#Options">¶</a></h2><p>The following options are understood:</p><div class="variablelist"><dl class="variablelist"><dt id="-h"><span class="term"><code class="option">-h</code>, </span><span class="term"><code class="option">--help</code></span><a class="headerlink" title="Permalink to this term" href="#-h">¶</a></dt><dd><p>Prints a short help
|
|
text and exits.</p></dd><dt id="--version"><span class="term"><code class="option">--version</code></span><a class="headerlink" title="Permalink to this term" href="#--version">¶</a></dt><dd><p>Prints a short version string and exits.</p></dd><dt id="-t"><span class="term"><code class="option">-t</code>, </span><span class="term"><code class="option">--type=</code></span><a class="headerlink" title="Permalink to this term" href="#-t">¶</a></dt><dd><p>The argument should be a comma separated list of unit
|
|
types such as <code class="option">service</code> and
|
|
<code class="option">socket</code>, or unit load states such as
|
|
<code class="option">loaded</code> and <code class="option">masked</code>
|
|
(types and states can be mixed).</p><p>If one of the arguments is a unit type, when listing
|
|
units, limit display to certain unit types. Otherwise units
|
|
of all types will be shown.</p><p>If one of the arguments is a unit load state, when
|
|
listing units, limit display to certain unit
|
|
types. Otherwise units of in all load states will be
|
|
shown.</p><p>As a special case, if one of the arguments is
|
|
<code class="option">help</code>, a list of allowed values will be
|
|
printed and the program will exit.</p></dd><dt id="-p"><span class="term"><code class="option">-p</code>, </span><span class="term"><code class="option">--property=</code></span><a class="headerlink" title="Permalink to this term" href="#-p">¶</a></dt><dd><p>When showing unit/job/manager properties with the
|
|
<span class="command"><strong>show</strong></span> command, limit display to certain
|
|
properties as specified as argument. If not specified all
|
|
set properties are shown. The argument should be a
|
|
comma-separated list of property names, such as
|
|
<code class="literal">MainPID</code>. If specified more than once all
|
|
properties with the specified names are shown.</p></dd><dt id="-a"><span class="term"><code class="option">-a</code>, </span><span class="term"><code class="option">--all</code></span><a class="headerlink" title="Permalink to this term" href="#-a">¶</a></dt><dd><p>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.</p><p>To list all units installed on the system, use the
|
|
<span class="command"><strong>list-unit-files</strong></span> command instead.</p></dd><dt id="--reverse"><span class="term"><code class="option">--reverse</code></span><a class="headerlink" title="Permalink to this term" href="#--reverse">¶</a></dt><dd><p>Show reverse dependencies between units with
|
|
<span class="command"><strong>list-dependencies</strong></span>, i.e. units with
|
|
dependencies of type <code class="varname">Wants=</code> or
|
|
<code class="varname">Requires=</code> on the given unit.
|
|
</p></dd><dt id="--after"><span class="term"><code class="option">--after</code>, </span><span class="term"><code class="option">--before</code></span><a class="headerlink" title="Permalink to this term" href="#--after">¶</a></dt><dd><p>Show which units are started after, resp. before
|
|
with <span class="command"><strong>list-dependencies</strong></span>.
|
|
</p></dd><dt id="--failed"><span class="term"><code class="option">--failed</code></span><a class="headerlink" title="Permalink to this term" href="#--failed">¶</a></dt><dd><p>When listing units, show only failed units. Do not
|
|
confuse with <code class="option">--fail</code>.</p></dd><dt id="--full"><span class="term"><code class="option">--full</code></span><a class="headerlink" title="Permalink to this term" href="#--full">¶</a></dt><dd><p>Do not ellipsize unit names, cgroup members, and
|
|
truncate unit descriptions in the output of
|
|
<span class="command"><strong>list-units</strong></span> and
|
|
<span class="command"><strong>list-jobs</strong></span>.</p></dd><dt id="--fail"><span class="term"><code class="option">--fail</code></span><a class="headerlink" title="Permalink to this term" href="#--fail">¶</a></dt><dd><p>If the requested operation conflicts with a pending
|
|
unfinished job, fail the command. If this is not specified
|
|
the requested operation will replace the pending job, if
|
|
necessary. Do not confuse with
|
|
<code class="option">--failed</code>.</p></dd><dt id="--show-types"><span class="term"><code class="option">--show-types</code></span><a class="headerlink" title="Permalink to this term" href="#--show-types">¶</a></dt><dd><p>When showing sockets, show the type of the socket.</p></dd><dt id="--irreversible"><span class="term"><code class="option">--irreversible</code></span><a class="headerlink" title="Permalink to this term" href="#--irreversible">¶</a></dt><dd><p>Mark this transaction's jobs as irreversible. This prevents
|
|
future conflicting transactions from replacing these jobs.
|
|
The jobs can still be cancelled using the <span class="command"><strong>cancel</strong></span>
|
|
command.</p></dd><dt id="--ignore-dependencies"><span class="term"><code class="option">--ignore-dependencies</code></span><a class="headerlink" title="Permalink to this term" href="#--ignore-dependencies">¶</a></dt><dd><p>When enqueuing a new job ignore all its dependencies
|
|
and execute it 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.</p></dd><dt id="-i"><span class="term"><code class="option">-i</code>, </span><span class="term"><code class="option">--ignore-inhibitors</code></span><a class="headerlink" title="Permalink to this term" href="#-i">¶</a></dt><dd><p>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 a list of active locks
|
|
is printed. However if <code class="option">--ignore-inhibitors</code>
|
|
is specified the locks are ignored and not printed, and the
|
|
operation attempted anyway, possibly requiring additional
|
|
privileges.</p></dd><dt id="-q"><span class="term"><code class="option">-q</code>, </span><span class="term"><code class="option">--quiet</code></span><a class="headerlink" title="Permalink to this term" href="#-q">¶</a></dt><dd><p>Suppress output to standard output in
|
|
<span class="command"><strong>snapshot</strong></span>,
|
|
<span class="command"><strong>is-active</strong></span>,
|
|
<span class="command"><strong>is-failed</strong></span>,
|
|
<span class="command"><strong>enable</strong></span> and
|
|
<span class="command"><strong>disable</strong></span>.</p></dd><dt id="--no-block"><span class="term"><code class="option">--no-block</code></span><a class="headerlink" title="Permalink to this term" href="#--no-block">¶</a></dt><dd><p>Do not synchronously wait for the requested operation
|
|
to finish. If this is not specified the job will be
|
|
verified, enqueued and <span class="command"><strong>systemctl</strong></span> will
|
|
wait until it is completed. By passing this argument it is
|
|
only verified and enqueued.</p></dd><dt id="--no-legend"><span class="term"><code class="option">--no-legend</code></span><a class="headerlink" title="Permalink to this term" href="#--no-legend">¶</a></dt><dd><p>Do not print a legend, i.e. the column headers and
|
|
the footer with hints.</p></dd><dt id="--no-pager"><span class="term"><code class="option">--no-pager</code></span><a class="headerlink" title="Permalink to this term" href="#--no-pager">¶</a></dt><dd><p>Do not pipe output into a pager.</p></dd><dt id="--system"><span class="term"><code class="option">--system</code></span><a class="headerlink" title="Permalink to this term" href="#--system">¶</a></dt><dd><p>Talk to the systemd system manager. (Default)</p></dd><dt id="--user"><span class="term"><code class="option">--user</code></span><a class="headerlink" title="Permalink to this term" href="#--user">¶</a></dt><dd><p>Talk to the systemd manager of the calling
|
|
user.</p></dd><dt id="--no-wall"><span class="term"><code class="option">--no-wall</code></span><a class="headerlink" title="Permalink to this term" href="#--no-wall">¶</a></dt><dd><p>Don't send wall message before halt, power-off,
|
|
reboot.</p></dd><dt id="--global"><span class="term"><code class="option">--global</code></span><a class="headerlink" title="Permalink to this term" href="#--global">¶</a></dt><dd><p>When used with <span class="command"><strong>enable</strong></span> and
|
|
<span class="command"><strong>disable</strong></span>, operate on the global user
|
|
configuration directory, thus enabling or disabling a unit
|
|
file globally for all future logins of all users.</p></dd><dt id="--no-reload"><span class="term"><code class="option">--no-reload</code></span><a class="headerlink" title="Permalink to this term" href="#--no-reload">¶</a></dt><dd><p>When used with <span class="command"><strong>enable</strong></span> and
|
|
<span class="command"><strong>disable</strong></span>, do not implicitly reload daemon
|
|
configuration after executing the changes.</p></dd><dt id="--no-ask-password"><span class="term"><code class="option">--no-ask-password</code></span><a class="headerlink" title="Permalink to this term" href="#--no-ask-password">¶</a></dt><dd><p>When used with <span class="command"><strong>start</strong></span> and related
|
|
commands, disables asking for passwords. Background services
|
|
may require input of a password or passphrase string, for
|
|
example to unlock system hard disks or cryptographic
|
|
certificates. Unless this option is specified and the
|
|
command is invoked from a terminal
|
|
<span class="command"><strong>systemctl</strong></span> will query the user on the
|
|
terminal for the necessary secrets. Use this option to
|
|
switch this behavior off. In this case the password must be
|
|
supplied by some other means (for example graphical password
|
|
agents) or the service might fail. This also disables
|
|
querying the user for authentication for privileged
|
|
operations.</p></dd><dt id="--kill-who="><span class="term"><code class="option">--kill-who=</code></span><a class="headerlink" title="Permalink to this term" href="#--kill-who=">¶</a></dt><dd><p>When used with <span class="command"><strong>kill</strong></span>, choose which
|
|
processes to kill. Must be one of <code class="option">main</code>,
|
|
<code class="option">control</code> or <code class="option">all</code> to select
|
|
whether to kill only the main process of the unit, the
|
|
control process or all processes of the unit. If omitted
|
|
defaults to <code class="option">all</code>.</p></dd><dt id="-s"><span class="term"><code class="option">-s</code>, </span><span class="term"><code class="option">--signal=</code></span><a class="headerlink" title="Permalink to this term" href="#-s">¶</a></dt><dd><p>When used with <span class="command"><strong>kill</strong></span>, choose which
|
|
signal to send to selected processes. Must be one of the
|
|
well known signal specifiers such as SIGTERM, SIGINT or
|
|
SIGSTOP. If omitted defaults to
|
|
<code class="option">SIGTERM</code>.</p></dd><dt id="-f"><span class="term"><code class="option">-f</code>, </span><span class="term"><code class="option">--force</code></span><a class="headerlink" title="Permalink to this term" href="#-f">¶</a></dt><dd><p>When used with <span class="command"><strong>enable</strong></span>, overwrite
|
|
any existing conflicting symlinks.</p><p>When used with <span class="command"><strong>halt</strong></span>,
|
|
<span class="command"><strong>poweroff</strong></span>, <span class="command"><strong>reboot</strong></span> or
|
|
<span class="command"><strong>kexec</strong></span> execute the selected operation
|
|
without shutting down all units. However, all processes will
|
|
be killed forcibly and all file systems are unmounted or
|
|
remounted read-only. This is hence a drastic but relatively
|
|
safe option to request an immediate reboot. If
|
|
<code class="option">--force</code> is specified twice for these
|
|
operations, they will be executed immediately without
|
|
terminating any processes or umounting any file
|
|
systems. Warning: specifying <code class="option">--force</code> twice
|
|
with any of these operations might result in data
|
|
loss.</p></dd><dt id="--root="><span class="term"><code class="option">--root=</code></span><a class="headerlink" title="Permalink to this term" href="#--root=">¶</a></dt><dd><p>When used with
|
|
<span class="command"><strong>enable</strong></span>/<span class="command"><strong>disable</strong></span>/<span class="command"><strong>is-enabled</strong></span>
|
|
(and related commands), use alternative root path when
|
|
looking for unit files.</p></dd><dt id="--runtime"><span class="term"><code class="option">--runtime</code></span><a class="headerlink" title="Permalink to this term" href="#--runtime">¶</a></dt><dd><p>When used with <span class="command"><strong>enable</strong></span>,
|
|
<span class="command"><strong>disable</strong></span>, <span class="command"><strong>is-enabled</strong></span>
|
|
(and related commands), make changes only temporarily, so
|
|
that they are lost on the next reboot. This will have the
|
|
effect that changes are not made in subdirectories of
|
|
<code class="filename">/etc</code> but in <code class="filename">/run</code>,
|
|
with identical immediate effects, however, since the latter
|
|
is lost on reboot, the changes are lost too.</p><p>Similar, when used with
|
|
<span class="command"><strong>set-cgroup-attr</strong></span>,
|
|
<span class="command"><strong>unset-cgroup-attr</strong></span>,
|
|
<span class="command"><strong>set-cgroup</strong></span> and
|
|
<span class="command"><strong>unset-cgroup</strong></span>, make changes only
|
|
temporarily, so that they are lost on the next
|
|
reboot.</p></dd><dt id="-H"><span class="term"><code class="option">-H</code>, </span><span class="term"><code class="option">--host</code></span><a class="headerlink" title="Permalink to this term" href="#-H">¶</a></dt><dd><p>Execute operation remotely. Specify a hostname, or
|
|
username and hostname separated by @, to connect to. This
|
|
will use SSH to talk to the remote systemd
|
|
instance.</p></dd><dt id="-P"><span class="term"><code class="option">-P</code>, </span><span class="term"><code class="option">--privileged</code></span><a class="headerlink" title="Permalink to this term" href="#-P">¶</a></dt><dd><p>Acquire privileges via PolicyKit before executing the
|
|
operation.</p></dd><dt id="-n"><span class="term"><code class="option">-n</code>, </span><span class="term"><code class="option">--lines=</code></span><a class="headerlink" title="Permalink to this term" href="#-n">¶</a></dt><dd><p>When used with <span class="command"><strong>status</strong></span> controls the
|
|
number of journal lines to show, counting from the most
|
|
recent ones. Takes a positive integer argument. Defaults to
|
|
10.</p></dd><dt id="-o"><span class="term"><code class="option">-o</code>, </span><span class="term"><code class="option">--output=</code></span><a class="headerlink" title="Permalink to this term" href="#-o">¶</a></dt><dd><p>When used with <span class="command"><strong>status</strong></span> controls the
|
|
formatting of the journal entries that are shown. For the
|
|
available choices see
|
|
<a href="journalctl.html"><span class="citerefentry"><span class="refentrytitle">journalctl</span>(1)</span></a>.
|
|
Defaults to <code class="literal">short</code>.</p></dd><dt id="--plain"><span class="term"><code class="option">--plain</code></span><a class="headerlink" title="Permalink to this term" href="#--plain">¶</a></dt><dd><p>When used with <span class="command"><strong>list-dependencies</strong></span>
|
|
the output is printed as a list instead of a tree.</p></dd></dl></div></div><div class="refsect1"><a name="idm259764225648"></a><h2 id="Commands">Commands<a class="headerlink" title="Permalink to this headline" href="#Commands">¶</a></h2><p>The following commands are understood:</p><div class="variablelist"><dl class="variablelist"><dt id="list-units"><span class="term"><span class="command"><strong>list-units</strong></span></span><a class="headerlink" title="Permalink to this term" href="#list-units">¶</a></dt><dd><p>List known units (subject to limitations specified
|
|
with <code class="option">-t</code>).</p><p>This is the default command.</p></dd><dt id="list-sockets"><span class="term"><span class="command"><strong>list-sockets</strong></span></span><a class="headerlink" title="Permalink to this term" href="#list-sockets">¶</a></dt><dd><p>List socket units ordered by the listening address. Produces output
|
|
similar to
|
|
</p><pre class="programlisting">
|
|
LISTEN UNIT ACTIVATES
|
|
/dev/initctl systemd-initctl.socket systemd-initctl.service
|
|
...
|
|
[::]:22 sshd.socket sshd.service
|
|
kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service
|
|
|
|
5 sockets listed.
|
|
</pre><p>
|
|
Note: because the addresses might contains spaces, this output
|
|
is not suitable for programatic consumption.
|
|
</p><p>See also the options <code class="option">--show-types</code>,
|
|
<code class="option">--all</code>, and <code class="option">--failed</code>.</p></dd><dt id="start NAME..."><span class="term"><span class="command"><strong>start <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#start%20NAME...">¶</a></dt><dd><p>Start (activate) one or more units specified on the
|
|
command line.</p></dd><dt id="stop NAME..."><span class="term"><span class="command"><strong>stop <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#stop%20NAME...">¶</a></dt><dd><p>Stop (deactivate) one or more units specified on the
|
|
command line.</p></dd><dt id="reload NAME..."><span class="term"><span class="command"><strong>reload <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#reload%20NAME...">¶</a></dt><dd><p>Asks all units listed on the command line to reload
|
|
their configuration. Note that this will reload the
|
|
service-specific configuration, not the unit configuration
|
|
file of systemd. If you want systemd to reload the
|
|
configuration file of a unit use the
|
|
<span class="command"><strong>daemon-reload</strong></span> command. In other words:
|
|
for the example case of Apache, this will reload Apache's
|
|
<code class="filename">httpd.conf</code> in the web server, not the
|
|
<code class="filename">apache.service</code> systemd unit
|
|
file. </p><p>This command should not be confused with the
|
|
<span class="command"><strong>daemon-reload</strong></span> or <span class="command"><strong>load</strong></span>
|
|
commands.</p></dd><dt id="restart NAME..."><span class="term"><span class="command"><strong>restart <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#restart%20NAME...">¶</a></dt><dd><p>Restart one or more units specified on the command
|
|
line. If the units are not running yet they will be
|
|
started.</p></dd><dt id="try-restart NAME..."><span class="term"><span class="command"><strong>try-restart <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#try-restart%20NAME...">¶</a></dt><dd><p>Restart one or more units specified on the command
|
|
line if the units are running. Do nothing if units are not
|
|
running. Note that for compatibility with Red Hat init
|
|
scripts <span class="command"><strong>condrestart</strong></span> is equivalent to this
|
|
command.</p></dd><dt id="reload-or-restart NAME..."><span class="term"><span class="command"><strong>reload-or-restart <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#reload-or-restart%20NAME...">¶</a></dt><dd><p>Reload one or more units if they support it. If not,
|
|
restart them instead. If the units are not running yet they
|
|
will be started.</p></dd><dt id="reload-or-try-restart NAME..."><span class="term"><span class="command"><strong>reload-or-try-restart <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#reload-or-try-restart%20NAME...">¶</a></dt><dd><p>Reload one or more units if they support it. If not,
|
|
restart them instead. Do nothing if the units are not
|
|
running. Note that for compatibility with SysV init scripts
|
|
<span class="command"><strong>force-reload</strong></span> is equivalent to this
|
|
command.</p></dd><dt id="isolate NAME"><span class="term"><span class="command"><strong>isolate <em class="replaceable"><code>NAME</code></em></strong></span></span><a class="headerlink" title="Permalink to this term" href="#isolate%20NAME">¶</a></dt><dd><p>Start the unit specified on the command line and its
|
|
dependencies and stop all others.</p><p>This is similar to changing the runlevel in a
|
|
traditional init system. The <span class="command"><strong>isolate</strong></span>
|
|
command will immediately stop processes that are not enabled
|
|
in the new unit, possibly including the graphical
|
|
environment or terminal you are currently using.</p><p>Note that this is allowed only on units where
|
|
<code class="option">AllowIsolate=</code> is enabled. See
|
|
<a href="systemd.unit.html"><span class="citerefentry"><span class="refentrytitle">systemd.unit</span>(5)</span></a>
|
|
for details.</p></dd><dt id="kill NAME..."><span class="term"><span class="command"><strong>kill <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#kill%20NAME...">¶</a></dt><dd><p>Send a signal to one or more processes of the
|
|
unit. Use <code class="option">--kill-who=</code> to select which
|
|
process to kill. Use <code class="option">--kill-mode=</code> to select
|
|
the kill mode and <code class="option">--signal=</code> to select the
|
|
signal to send.</p></dd><dt id="is-active NAME..."><span class="term"><span class="command"><strong>is-active <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#is-active%20NAME...">¶</a></dt><dd><p>Check whether any of the specified units are active
|
|
(i.e. running). Returns an exit code 0 if at least one is
|
|
active, non-zero otherwise. Unless <code class="option">--quiet</code>
|
|
is specified this will also print the current unit state to
|
|
STDOUT.</p></dd><dt id="is-failed NAME..."><span class="term"><span class="command"><strong>is-failed <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#is-failed%20NAME...">¶</a></dt><dd><p>Check whether any of the specified units are failed.
|
|
Returns an exit code 0 if at least one is failed, non-zero
|
|
otherwise. Unless <code class="option">--quiet</code> is specified this
|
|
will also print the current unit state to
|
|
STDOUT.</p></dd><dt id="status [NAME...|PID...]"><span class="term"><span class="command"><strong>status [<em class="replaceable"><code>NAME</code></em>...|<em class="replaceable"><code>PID</code></em>...]</strong></span></span><a class="headerlink" title="Permalink to this term" href="#status%20%5BNAME...%7CPID...%5D">¶</a></dt><dd><p>Show terse runtime status information about one or
|
|
more units, followed by most recent log data from the
|
|
journal. If no units are specified, show all units (subject
|
|
to limitations specified with <code class="option">-t</code>). If a PID
|
|
is passed show information about the unit the process
|
|
belongs to.</p><p>This function is intended to generate human-readable
|
|
output. If you are looking for computer-parsable output, use
|
|
<span class="command"><strong>show</strong></span> instead.</p></dd><dt id="show [NAME...|JOB...]"><span class="term"><span class="command"><strong>show [<em class="replaceable"><code>NAME</code></em>...|<em class="replaceable"><code>JOB</code></em>...]</strong></span></span><a class="headerlink" title="Permalink to this term" href="#show%20%5BNAME...%7CJOB...%5D">¶</a></dt><dd><p>Show properties of one or more units, jobs, or the
|
|
manager itself. If no argument is specified properties of
|
|
the manager will be shown. If a unit name is specified
|
|
properties of the unit is shown, and if a job id is
|
|
specified properties of the job is shown. By default, empty
|
|
properties are suppressed. Use <code class="option">--all</code> to
|
|
show those too. To select specific properties to show use
|
|
<code class="option">--property=</code>. This command is intended to be
|
|
used whenever computer-parsable output is required. Use
|
|
<span class="command"><strong>status</strong></span> if you are looking for formatted
|
|
human-readable output.</p></dd><dt id="get-cgroup-attr NAME ATTRIBUTE..."><span class="term"><span class="command"><strong>get-cgroup-attr <em class="replaceable"><code>NAME</code></em> <em class="replaceable"><code>ATTRIBUTE</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#get-cgroup-attr%20NAME%20ATTRIBUTE...">¶</a></dt><dd><p>Retrieve the specified control group attributes of the
|
|
specified unit. Takes a unit name and one or more attribute
|
|
names such as <code class="literal">cpu.shares</code>. This will
|
|
output the current values of the specified attributes,
|
|
separated by new-lines. For attributes that take list of
|
|
items the output will be new-line separated, too. This
|
|
operation will always try to retrieve the data in question
|
|
from the kernel first, and if that is not available use the
|
|
configured values instead. Instead of low-level control
|
|
group attribute names high-level pretty names may be used,
|
|
as used for unit execution environment configuration, see
|
|
<a href="systemd.exec.html"><span class="citerefentry"><span class="refentrytitle">systemd.exec</span>(5)</span></a>
|
|
for details. For example, passing
|
|
<code class="literal">memory.limit_in_bytes</code> and
|
|
<code class="literal">MemoryLimit</code> is equivalent.</p></dd><dt id="set-cgroup-attr NAME ATTRIBUTE VALUE..."><span class="term"><span class="command"><strong>set-cgroup-attr <em class="replaceable"><code>NAME</code></em> <em class="replaceable"><code>ATTRIBUTE</code></em> <em class="replaceable"><code>VALUE</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#set-cgroup-attr%20NAME%20ATTRIBUTE%20VALUE...">¶</a></dt><dd><p>Set the specified control group attribute of the
|
|
specified unit to the specified value. Takes a unit
|
|
name and an attribute name such as
|
|
<code class="literal">cpu.shares</code>, plus one or more values
|
|
(multiple values may only be used for attributes that take
|
|
multiple values). This operation will immediately update the
|
|
kernel attribute for this unit and persistently store this
|
|
setting for later reboots (unless <code class="option">--runtime</code>
|
|
is passed, in which case the setting is not saved
|
|
persistently and only valid until the next reboot.) Instead
|
|
of low-level control group attribute names high-level pretty
|
|
names may be used, as used for unit execution environment
|
|
configuration, see
|
|
<a href="systemd.exec.html"><span class="citerefentry"><span class="refentrytitle">systemd.exec</span>(5)</span></a>
|
|
for details. For example, passing
|
|
<code class="literal">memory.limit_in_bytes</code> and
|
|
<code class="literal">MemoryLimit</code> is equivalent. This operation
|
|
will implicitly create a control group for the unit in the
|
|
controller the attribute belongs to, if needed. For
|
|
attributes that take multiple values, this operation will
|
|
append the specified values to the previously set values
|
|
list (use <span class="command"><strong>unset-cgroup-attr</strong></span> to reset the
|
|
list explicitly). For attributes that take a single value
|
|
only the list will be reset implicitly.</p></dd><dt id="unset-cgroup-attr NAME ATTRIBUTE..."><span class="term"><span class="command"><strong>unset-cgroup-attr <em class="replaceable"><code>NAME</code></em> <em class="replaceable"><code>ATTRIBUTE</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#unset-cgroup-attr%20NAME%20ATTRIBUTE...">¶</a></dt><dd><p>Unset the specified control group attributes
|
|
of the specified unit. Takes a unit name and one or more
|
|
attribut names such as <code class="literal">cpu.shares</code>. This
|
|
operation might or might not have an immediate effect on the
|
|
current kernel attribute value. This will remove any
|
|
persistently stored configuration values for this attribute
|
|
(as set with <span class="command"><strong>set-cgroup-attr</strong></span> before),
|
|
unless <code class="option">--runtime</code> is passed, in which case the
|
|
configuration is reset only until the next reboot. Again,
|
|
high-level control group attributes may be used instead of the
|
|
low-level kernel ones. For attributes which take multiple
|
|
values, all currently set values are reset.</p></dd><dt id="set-cgroup NAME CGROUP..."><span class="term"><span class="command"><strong>set-cgroup <em class="replaceable"><code>NAME</code></em> <em class="replaceable"><code>CGROUP</code></em>...</strong></span>, </span><span class="term"><span class="command"><strong>unset-cgroup <em class="replaceable"><code>NAME</code></em> <em class="replaceable"><code>CGROUP</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#set-cgroup%20NAME%20CGROUP...">¶</a></dt><dd><p>Add or remove a unit to/from a specific
|
|
control group hierarchy and/or control group path. Takes a
|
|
unit name, plus a control group specification in the syntax
|
|
<em class="replaceable"><code>CONTROLLER</code></em>:<em class="replaceable"><code>PATH</code></em>
|
|
or <em class="replaceable"><code>CONTROLLER</code></em>. In the latter syntax
|
|
(where the path is omitted) the default unit control group
|
|
path is implied. Examples: <code class="literal">cpu</code> or
|
|
<code class="literal">cpu:/foo/bar</code>. If a unit is removed from a
|
|
control group hierarchy all its processes will be moved to the
|
|
root group of the hierarchy and all control group attributes
|
|
will be reset. These operations are immediately reflected in
|
|
the kernel hierarchy, and stored persistently to disk (unless
|
|
<code class="option">--runtime</code> is passed).</p></dd><dt id="help NAME...|PID..."><span class="term"><span class="command"><strong>help <em class="replaceable"><code>NAME</code></em>...|<em class="replaceable"><code>PID</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#help%20NAME...%7CPID...">¶</a></dt><dd><p>Show manual pages for one or more units, if
|
|
available. If a PID is passed the manual pages for the unit
|
|
the process of the PID belongs to is
|
|
shown.</p></dd><dt id="reset-failed [NAME...]"><span class="term"><span class="command"><strong>reset-failed [<em class="replaceable"><code>NAME</code></em>...]</strong></span></span><a class="headerlink" title="Permalink to this term" href="#reset-failed%20%5BNAME...%5D">¶</a></dt><dd><p>Reset the <code class="literal">failed</code> state of the
|
|
specified units, or if no unit name is passed of all
|
|
units. When a unit fails in some way (i.e. process exiting
|
|
with non-zero error code, terminating abnormally or timing
|
|
out) it will automatically enter the
|
|
<code class="literal">failed</code> state and its exit code and status
|
|
is recorded for introspection by the administrator until the
|
|
service is restarted or reset with this command.</p></dd><dt id="list-unit-files"><span class="term"><span class="command"><strong>list-unit-files</strong></span></span><a class="headerlink" title="Permalink to this term" href="#list-unit-files">¶</a></dt><dd><p>List installed unit files.</p></dd><dt id="enable NAME..."><span class="term"><span class="command"><strong>enable <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#enable%20NAME...">¶</a></dt><dd><p>Enable one or more unit files or unit file instances,
|
|
as specified on the command line. This will create a number
|
|
of symlinks as encoded in the <code class="literal">[Install]</code>
|
|
sections of the unit files. After the symlinks have been
|
|
created the systemd configuration is reloaded (in a way that
|
|
is equivalent to <span class="command"><strong>daemon-reload</strong></span>) to ensure
|
|
the changes are taken into account immediately. Note that
|
|
this does not have the effect that any of the units enabled
|
|
are also started at the same time. If this is desired a
|
|
separate <span class="command"><strong>start</strong></span> command must be invoked
|
|
for the unit. Also note that in case of instance enablement,
|
|
symlinks named same as instances are created in install
|
|
location, however they all point to the same template unit
|
|
file.</p><p>This command will print the actions executed. This
|
|
output may be suppressed by passing <code class="option">--quiet</code>.
|
|
</p><p>Note that this operation creates only the suggested
|
|
symlinks for the units. While this command is the
|
|
recommended way to manipulate the unit configuration
|
|
directory, the administrator is free to make additional
|
|
changes manually, by placing or removing symlinks in the
|
|
directory. This is particularly useful to create
|
|
configurations that deviate from the suggested default
|
|
installation. In this case the administrator must make sure
|
|
to invoke <span class="command"><strong>daemon-reload</strong></span> manually as
|
|
necessary, to ensure his changes are taken into account.
|
|
</p><p>Enabling units should not be confused with starting
|
|
(activating) units, as done by the <span class="command"><strong>start</strong></span>
|
|
command. Enabling and starting units is orthogonal: units
|
|
may be enabled without being started and started without
|
|
being enabled. Enabling simply hooks the unit into various
|
|
suggested places (for example, so that the unit is
|
|
automatically started on boot or when a particular kind of
|
|
hardware is plugged in). Starting actually spawns the daemon
|
|
process (in case of service units), or binds the socket (in
|
|
case of socket units), and so on.</p><p>Depending on whether <code class="option">--system</code>,
|
|
<code class="option">--user</code> or <code class="option">--global</code> is
|
|
specified this enables the unit for the system, for the
|
|
calling user only or for all future logins of all
|
|
users. Note that in the last case no systemd daemon
|
|
configuration is reloaded.</p></dd><dt id="disable NAME..."><span class="term"><span class="command"><strong>disable <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#disable%20NAME...">¶</a></dt><dd><p>Disables one or more units. This removes all symlinks
|
|
to the specified unit files from the unit configuration
|
|
directory, and hence undoes the changes made by
|
|
<span class="command"><strong>enable</strong></span>. Note however that this removes
|
|
all symlinks to the unit files (i.e. including manual
|
|
additions), not just those actually created by
|
|
<span class="command"><strong>enable</strong></span>. This call implicitly reloads the
|
|
systemd daemon configuration after completing the disabling
|
|
of the units. Note that this command does not implicitly
|
|
stop the units that are being disabled. If this is desired
|
|
an additional <span class="command"><strong>stop</strong></span> command should be
|
|
executed afterwards.</p><p>This command will print the actions executed. This
|
|
output may be suppressed by passing <code class="option">--quiet</code>.
|
|
</p><p>This command honors <code class="option">--system</code>,
|
|
<code class="option">--user</code>, <code class="option">--global</code> in a
|
|
similar way as <span class="command"><strong>enable</strong></span>.</p></dd><dt id="is-enabled NAME..."><span class="term"><span class="command"><strong>is-enabled <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#is-enabled%20NAME...">¶</a></dt><dd><p>Checks whether any of the specified unit files are
|
|
enabled (as with <span class="command"><strong>enable</strong></span>). Returns an exit
|
|
code of 0 if at least one is enabled, non-zero
|
|
otherwise. Prints the current enable status. To suppress
|
|
this output use <code class="option">--quiet</code>.</p></dd><dt id="reenable NAME..."><span class="term"><span class="command"><strong>reenable <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#reenable%20NAME...">¶</a></dt><dd><p>Reenable one or more unit files, as specified on the
|
|
command line. This is a combination of
|
|
<span class="command"><strong>disable</strong></span> and <span class="command"><strong>enable</strong></span> and
|
|
is useful to reset the symlinks a unit is enabled with to
|
|
the defaults configured in the <code class="literal">[Install]</code>
|
|
section of the unit file.</p></dd><dt id="preset NAME..."><span class="term"><span class="command"><strong>preset <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#preset%20NAME...">¶</a></dt><dd><p>Reset one or more unit files, as specified on the
|
|
command line, to the defaults configured in the preset
|
|
policy files. This has the same effect as
|
|
<span class="command"><strong>disable</strong></span> or <span class="command"><strong>enable</strong></span>,
|
|
depending how the unit is listed in the preset files. For
|
|
more information on preset policy format see
|
|
<a href="systemd.preset.html"><span class="citerefentry"><span class="refentrytitle">systemd.preset</span>(5)</span></a>.
|
|
For more information on the concept of presets please
|
|
consult the
|
|
<a class="ulink" href="http://freedesktop.org/wiki/Software/systemd/Preset" target="_top">Preset</a>
|
|
document.</p></dd><dt id="mask NAME..."><span class="term"><span class="command"><strong>mask <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#mask%20NAME...">¶</a></dt><dd><p>Mask one or more unit files, as specified on the
|
|
command line. This will link these units to
|
|
<code class="filename">/dev/null</code>, making it impossible to
|
|
start them. This is a stronger version of
|
|
<span class="command"><strong>disable</strong></span>, since it prohibits all kinds of
|
|
activation of the unit, including manual activation. Use
|
|
this option with care.</p></dd><dt id="unmask NAME..."><span class="term"><span class="command"><strong>unmask <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#unmask%20NAME...">¶</a></dt><dd><p>Unmask one or more unit files, as specified on the
|
|
command line. This will undo the effect of
|
|
<span class="command"><strong>mask</strong></span>.</p></dd><dt id="link FILENAME..."><span class="term"><span class="command"><strong>link <em class="replaceable"><code>FILENAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#link%20FILENAME...">¶</a></dt><dd><p>Link a unit file that is not in the unit file search
|
|
paths into the unit file search path. This requires an
|
|
absolute path to a unit file. The effect of this can be
|
|
undone with <span class="command"><strong>disable</strong></span>. The effect of this
|
|
command is that a unit file is available for
|
|
<span class="command"><strong>start</strong></span> and other commands although it
|
|
isn't installed directly in the unit search path.</p></dd><dt id="load NAME..."><span class="term"><span class="command"><strong>load <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#load%20NAME...">¶</a></dt><dd><p>Load one or more units specified on the command
|
|
line. This will simply load their configuration from disk,
|
|
but not start them. To start them you need to use the
|
|
<span class="command"><strong>start</strong></span> command which will implicitly load
|
|
a unit that has not been loaded yet. Note that systemd
|
|
garbage collects loaded units that are not active or
|
|
referenced by an active unit. This means that units loaded
|
|
this way will usually not stay loaded for long. Also note
|
|
that this command cannot be used to reload unit
|
|
configuration. Use the <span class="command"><strong>daemon-reload</strong></span>
|
|
command for that. All in all, this command is of little use
|
|
except for debugging.</p><p>This command should not be confused with the
|
|
<span class="command"><strong>daemon-reload</strong></span> or
|
|
<span class="command"><strong>reload</strong></span>.</p></dd><dt id="list-jobs"><span class="term"><span class="command"><strong>list-jobs</strong></span></span><a class="headerlink" title="Permalink to this term" href="#list-jobs">¶</a></dt><dd><p>List jobs that are in progress.</p></dd><dt id="cancel JOB..."><span class="term"><span class="command"><strong>cancel <em class="replaceable"><code>JOB</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#cancel%20JOB...">¶</a></dt><dd><p>Cancel one or more jobs specified on the command line
|
|
by their numeric job IDs. If no job id is specified, cancel
|
|
all pending jobs.</p></dd><dt id="dump"><span class="term"><span class="command"><strong>dump</strong></span></span><a class="headerlink" title="Permalink to this term" href="#dump">¶</a></dt><dd><p>Dump server status. This will output a (usually very
|
|
long) human readable manager status dump. Its format is
|
|
subject to change without notice and should not be parsed by
|
|
applications.</p></dd><dt id="list-dependencies NAME"><span class="term"><span class="command"><strong>list-dependencies <em class="replaceable"><code>NAME</code></em></strong></span></span><a class="headerlink" title="Permalink to this term" href="#list-dependencies%20NAME">¶</a></dt><dd><p>Shows required and wanted units of the specified
|
|
unit. If no unit is specified
|
|
<code class="filename">default.target</code> is implied. Target units
|
|
are recursively expanded. When <code class="option">--all</code> is
|
|
passed all other units are recursively expanded as
|
|
well.</p></dd><dt id="snapshot [NAME]"><span class="term"><span class="command"><strong>snapshot [<em class="replaceable"><code>NAME</code></em>]</strong></span></span><a class="headerlink" title="Permalink to this term" href="#snapshot%20%5BNAME%5D">¶</a></dt><dd><p>Create a snapshot. If a snapshot name is specified,
|
|
the new snapshot will be named after it. If none is
|
|
specified an automatic snapshot name is generated. In either
|
|
case, the snapshot name used is printed to STDOUT, unless
|
|
<code class="option">--quiet</code> is specified.</p><p>A snapshot refers to a saved state of the systemd
|
|
manager. It is implemented itself as a unit that is
|
|
generated dynamically with this command and has dependencies
|
|
on all units active at the time. At a later time the user
|
|
may return to this state by using the
|
|
<span class="command"><strong>isolate</strong></span> command on the snapshot unit.
|
|
</p><p>Snapshots are only useful for saving and restoring
|
|
which units are running or are stopped, they do not
|
|
save/restore any other state. Snapshots are dynamic and lost
|
|
on reboot.</p></dd><dt id="delete NAME..."><span class="term"><span class="command"><strong>delete <em class="replaceable"><code>NAME</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#delete%20NAME...">¶</a></dt><dd><p>Remove a snapshot previously created with
|
|
<span class="command"><strong>snapshot</strong></span>.</p></dd><dt id="daemon-reload"><span class="term"><span class="command"><strong>daemon-reload</strong></span></span><a class="headerlink" title="Permalink to this term" href="#daemon-reload">¶</a></dt><dd><p>Reload systemd manager configuration. This will reload
|
|
all unit files and recreate the entire dependency
|
|
tree. While the daemon is reloaded, all sockets systemd
|
|
listens on on behalf of user configuration will stay
|
|
accessible.</p><p>This command should not be confused
|
|
with the <span class="command"><strong>load</strong></span> or
|
|
<span class="command"><strong>reload</strong></span> commands.</p></dd><dt id="daemon-reexec"><span class="term"><span class="command"><strong>daemon-reexec</strong></span></span><a class="headerlink" title="Permalink to this term" href="#daemon-reexec">¶</a></dt><dd><p>Reexecute the systemd manager. This will serialize the
|
|
manager state, reexecute the process and deserialize the
|
|
state again. This command is of little use except for
|
|
debugging and package upgrades. Sometimes it might be
|
|
helpful as a heavy-weight <span class="command"><strong>daemon-reload</strong></span>.
|
|
While the daemon is reexecuted all sockets systemd listens
|
|
on on behalf of user configuration will stay accessible.
|
|
</p></dd><dt id="show-environment"><span class="term"><span class="command"><strong>show-environment</strong></span></span><a class="headerlink" title="Permalink to this term" href="#show-environment">¶</a></dt><dd><p>Dump the systemd manager environment block. The
|
|
environment block will be dumped in straight-forward form
|
|
suitable for sourcing into a shell script. This environment
|
|
block will be passed to all processes the manager
|
|
spawns.</p></dd><dt id="set-environment VARIABLE=VALUE..."><span class="term"><span class="command"><strong>set-environment <em class="replaceable"><code>VARIABLE=VALUE</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#set-environment%20VARIABLE=VALUE...">¶</a></dt><dd><p>Set one or more systemd manager environment variables,
|
|
as specified on the command line.</p></dd><dt id="unset-environment VARIABLE..."><span class="term"><span class="command"><strong>unset-environment <em class="replaceable"><code>VARIABLE</code></em>...</strong></span></span><a class="headerlink" title="Permalink to this term" href="#unset-environment%20VARIABLE...">¶</a></dt><dd><p>Unset one or more systemd manager environment
|
|
variables. If only a variable name is specified it will be
|
|
removed regardless of its value. If a variable and a value
|
|
are specified the variable is only removed if it has the
|
|
specified value.</p></dd><dt id="default"><span class="term"><span class="command"><strong>default</strong></span></span><a class="headerlink" title="Permalink to this term" href="#default">¶</a></dt><dd><p>Enter default mode. This is mostly equivalent to
|
|
<span class="command"><strong>isolate default.target</strong></span>.</p></dd><dt id="rescue"><span class="term"><span class="command"><strong>rescue</strong></span></span><a class="headerlink" title="Permalink to this term" href="#rescue">¶</a></dt><dd><p>Enter rescue mode. This is mostly equivalent to
|
|
<span class="command"><strong>isolate rescue.target</strong></span> but also prints a
|
|
wall message to all users.</p></dd><dt id="emergency"><span class="term"><span class="command"><strong>emergency</strong></span></span><a class="headerlink" title="Permalink to this term" href="#emergency">¶</a></dt><dd><p>Enter emergency mode. This is mostly equivalent to
|
|
<span class="command"><strong>isolate emergency.target</strong></span> but also prints
|
|
a wall message to all users.</p></dd><dt id="halt"><span class="term"><span class="command"><strong>halt</strong></span></span><a class="headerlink" title="Permalink to this term" href="#halt">¶</a></dt><dd><p>Shut down and halt the system. This is mostly equivalent to
|
|
<span class="command"><strong>start halt.target --irreversible</strong></span> but also
|
|
prints a wall message to all users. If combined with
|
|
<code class="option">--force</code> shutdown of all running services is
|
|
skipped, however all processes are killed and all file
|
|
systems are unmounted or mounted read-only, immediately
|
|
followed by the system halt. If <code class="option">--force</code> is
|
|
specified twice the operation is immediately executed
|
|
without terminating any processes or unmounting any file
|
|
systems. This may result in data loss.</p></dd><dt id="poweroff"><span class="term"><span class="command"><strong>poweroff</strong></span></span><a class="headerlink" title="Permalink to this term" href="#poweroff">¶</a></dt><dd><p>Shut down and power-off the system. This is mostly
|
|
equivalent to <span class="command"><strong>start poweroff.target --irreversible</strong></span>
|
|
but also prints a wall message to all users. If combined with
|
|
<code class="option">--force</code> shutdown of all running services is
|
|
skipped, however all processes are killed and all file
|
|
systems are unmounted or mounted read-only, immediately
|
|
followed by the powering off. If <code class="option">--force</code> is
|
|
specified twice the operation is immediately executed
|
|
without terminating any processes or unmounting any file
|
|
systems. This may result in data loss.</p></dd><dt id="reboot"><span class="term"><span class="command"><strong>reboot</strong></span></span><a class="headerlink" title="Permalink to this term" href="#reboot">¶</a></dt><dd><p>Shut down and reboot the system. This is mostly
|
|
equivalent to <span class="command"><strong>start reboot.target --irreversible</strong></span>
|
|
but also prints a wall message to all users. If combined with
|
|
<code class="option">--force</code> shutdown of all running services is
|
|
skipped, however all processes are killed and all file
|
|
systems are unmounted or mounted read-only, immediately
|
|
followed by the reboot. If <code class="option">--force</code> is
|
|
specified twice the operation is immediately executed
|
|
without terminating any processes or unmounting any file
|
|
systems. This may result in data loss.</p></dd><dt id="kexec"><span class="term"><span class="command"><strong>kexec</strong></span></span><a class="headerlink" title="Permalink to this term" href="#kexec">¶</a></dt><dd><p>Shut down and reboot the system via kexec. This is
|
|
mostly equivalent to <span class="command"><strong>start kexec.target --irreversible</strong></span>
|
|
but also prints a wall message to all users. If combined
|
|
with <code class="option">--force</code> shutdown of all running
|
|
services is skipped, however all processes are killed and
|
|
all file systems are unmounted or mounted read-only,
|
|
immediately followed by the reboot.</p></dd><dt id="exit"><span class="term"><span class="command"><strong>exit</strong></span></span><a class="headerlink" title="Permalink to this term" href="#exit">¶</a></dt><dd><p>Ask the systemd manager to quit. This is only
|
|
supported for user service managers (i.e. in conjunction
|
|
with the <code class="option">--user</code> option) and will fail
|
|
otherwise.</p></dd><dt id="suspend"><span class="term"><span class="command"><strong>suspend</strong></span></span><a class="headerlink" title="Permalink to this term" href="#suspend">¶</a></dt><dd><p>Suspend the system. This will trigger activation of
|
|
the special <code class="filename">suspend.target</code> target.
|
|
</p></dd><dt id="hibernate"><span class="term"><span class="command"><strong>hibernate</strong></span></span><a class="headerlink" title="Permalink to this term" href="#hibernate">¶</a></dt><dd><p>Hibernate the system. This will trigger activation of
|
|
the special <code class="filename">hibernate.target</code> target.
|
|
</p></dd><dt id="hybrid-sleep"><span class="term"><span class="command"><strong>hybrid-sleep</strong></span></span><a class="headerlink" title="Permalink to this term" href="#hybrid-sleep">¶</a></dt><dd><p>Hibernate and suspend the system. This will trigger
|
|
activation of the special
|
|
<code class="filename">hybrid-sleep.target</code> target.</p></dd><dt id="switch-root ROOT [INIT]"><span class="term"><span class="command"><strong>switch-root <em class="replaceable"><code>ROOT</code></em> [<em class="replaceable"><code>INIT</code></em>]</strong></span></span><a class="headerlink" title="Permalink to this term" href="#switch-root%20ROOT%20%5BINIT%5D">¶</a></dt><dd><p>Switches to a different root directory and executes a
|
|
new system manager process below it. This is intended for
|
|
usage in initial RAM disks ("initrd"), and will transition
|
|
from the initrd's system manager process (a.k.a "init"
|
|
process) to the main system manager process. Takes two
|
|
arguments: the directory to make the new root directory, and
|
|
the path to the new system manager binary below it to
|
|
execute as PID 1. If the latter is omitted or the empty
|
|
string, a systemd binary will automatically be searched for
|
|
and used as init. If the system manager path is omitted or
|
|
equal to the empty string the state of the initrd's system
|
|
manager process is passed to the main system manager, which
|
|
allows later introspection of the state of the services
|
|
involved in the initrd boot.</p></dd></dl></div></div><div class="refsect1"><a name="idm259764017200"></a><h2 id="Exit status">Exit status<a class="headerlink" title="Permalink to this headline" href="#Exit%20status">¶</a></h2><p>On success 0 is returned, a non-zero failure
|
|
code otherwise.</p></div><div class="refsect1"><a name="idm259764015968"></a><h2 id="Environment">Environment<a class="headerlink" title="Permalink to this headline" href="#Environment">¶</a></h2><div class="variablelist"><dl class="variablelist"><dt id="$SYSTEMD_PAGER"><span class="term"><code class="varname">$SYSTEMD_PAGER</code></span><a class="headerlink" title="Permalink to this term" href="#%24SYSTEMD_PAGER">¶</a></dt><dd><p>Pager to use when <code class="option">--no-pager</code> is not
|
|
given; overrides <code class="varname">$PAGER</code>. Setting this to
|
|
an empty string or the value <code class="literal">cat</code> is
|
|
equivalent to passing
|
|
<code class="option">--no-pager</code>.</p></dd></dl></div></div><div class="refsect1"><a name="idm259764011056"></a><h2 id="See Also">See Also<a class="headerlink" title="Permalink to this headline" href="#See%20Also">¶</a></h2><p>
|
|
<a href="systemd.html"><span class="citerefentry"><span class="refentrytitle">systemd</span>(1)</span></a>,
|
|
<a href="systemadm.html"><span class="citerefentry"><span class="refentrytitle">systemadm</span>(1)</span></a>,
|
|
<a href="journalctl.html"><span class="citerefentry"><span class="refentrytitle">journalctl</span>(1)</span></a>,
|
|
<a href="loginctl.html"><span class="citerefentry"><span class="refentrytitle">loginctl</span>(1)</span></a>,
|
|
<a href="systemd.unit.html"><span class="citerefentry"><span class="refentrytitle">systemd.unit</span>(5)</span></a>,
|
|
<a href="systemd.special.html"><span class="citerefentry"><span class="refentrytitle">systemd.special</span>(7)</span></a>,
|
|
<a href="wall.html"><span class="citerefentry"><span class="refentrytitle">wall</span>(1)</span></a>,
|
|
<a href="systemd.preset.html"><span class="citerefentry"><span class="refentrytitle">systemd.preset</span>(5)</span></a>
|
|
</p></div></div></body></html>
|