2 <!DOCTYPE refentry PUBLIC
"-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
4 <!ENTITY % entities SYSTEM
"custom-entities.ent" >
7 <!-- SPDX-License-Identifier: LGPL-2.1-or-later -->
9 <refentry id=
"systemctl"
10 xmlns:
xi=
"http://www.w3.org/2001/XInclude">
13 <title>systemctl
</title>
14 <productname>systemd
</productname>
18 <refentrytitle>systemctl
</refentrytitle>
19 <manvolnum>1</manvolnum>
23 <refname>systemctl
</refname>
24 <refpurpose>Control the systemd system and service manager
</refpurpose>
29 <command>systemctl
</command>
30 <arg choice=
"opt" rep=
"repeat">OPTIONS
</arg>
31 <arg choice=
"plain">COMMAND
</arg>
32 <arg choice=
"opt" rep=
"repeat">UNIT
</arg>
37 <title>Description
</title>
39 <para><command>systemctl
</command> may be used to introspect and
40 control the state of the
<literal>systemd
</literal> system and
41 service manager. Please refer to
42 <citerefentry><refentrytitle>systemd
</refentrytitle><manvolnum>1</manvolnum></citerefentry>
43 for an introduction into the basic concepts and functionality this
48 <title>Commands
</title>
50 <para>The following commands are understood:
</para>
53 <title>Unit Commands (Introspection and Modification)
</title>
57 <term><command>list-units
</command> <optional><replaceable>PATTERN
</replaceable>…
</optional></term>
60 <para>List units that
<command>systemd
</command> currently has in memory. This includes units that are
61 either referenced directly or through a dependency, units that are pinned by applications programmatically,
62 or units that were active in the past and have failed. By default only units which are active, have pending
63 jobs, or have failed are shown; this can be changed with option
<option>--all
</option>. If one or more
64 <replaceable>PATTERN
</replaceable>s are specified, only units matching one of them are shown. The units
65 that are shown are additionally filtered by
<option>--type=
</option> and
<option>--state=
</option> if those
66 options are specified.
</para>
68 <para>Note that this command does not show unit templates, but only instances of unit
69 templates. Units templates that aren't instantiated are not runnable, and will thus never show up
70 in the output of this command. Specifically this means that
<filename>foo@.service
</filename>
71 will never be shown in this list — unless instantiated, e.g. as
72 <filename>foo@bar.service
</filename>. Use
<command>list-unit-files
</command> (see below) for
73 listing installed unit template files.
</para>
75 <para>Produces output similar to
76 <programlisting> UNIT LOAD ACTIVE SUB DESCRIPTION
77 sys-module-fuse.device loaded active plugged /sys/module/fuse
78 -.mount loaded active mounted Root Mount
79 boot-efi.mount loaded active mounted /boot/efi
80 systemd-journald.service loaded active running Journal Service
81 systemd-logind.service loaded active running Login Service
82 ● user@
1000.service loaded failed failed User Manager for UID
1000
84 systemd-tmpfiles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
86 LOAD = Reflects whether the unit definition was properly loaded.
87 ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
88 SUB = The low-level unit activation state, values depend on unit type.
90 123 loaded units listed. Pass --all to see loaded but inactive units, too.
91 To show all installed unit files use 'systemctl list-unit-files'.
</programlisting></para>
93 <para>The header and the last unit of a given type are underlined if the terminal supports
94 that. A colored dot is shown next to services which were masked, not found, or otherwise
97 <para>The LOAD column shows the load state, one of
<constant>loaded
</constant>,
98 <constant>not-found
</constant>,
<constant>bad-setting
</constant>,
<constant>error
</constant>,
99 <constant>masked
</constant>. The ACTIVE columns shows the general unit state, one of
100 <constant>active
</constant>,
<constant>reloading
</constant>,
<constant>inactive
</constant>,
101 <constant>failed
</constant>,
<constant>activating
</constant>,
<constant>deactivating
</constant>. The SUB
102 column shows the unit-type-specific detailed state of the unit, possible values vary by unit type. The list
103 of possible LOAD, ACTIVE, and SUB states is not constant and new systemd releases may both add and remove
104 values.
<programlisting>systemctl --state=help
</programlisting> command may be used to display the
105 current set of possible values.
</para>
107 <para>This is the default command.
</para>
112 <term><command>list-automounts
</command> <optional><replaceable>PATTERN
</replaceable>…
</optional></term>
115 <para>List automount units currently in memory, ordered by mount path. If one or more
116 <replaceable>PATTERN
</replaceable>s are specified, only automount units matching one of them are shown.
117 Produces output similar to
119 WHAT WHERE MOUNTED IDLE TIMEOUT UNIT
120 /dev/sdb1 /mnt/test no
120s mnt-test.automount
121 binfmt_misc /proc/sys/fs/binfmt_misc yes
0 proc-sys-fs-binfmt_misc.automount
123 2 automounts listed.
</programlisting>
126 <para>Also see
<option>--show-types
</option>,
<option>--all
</option>, and
<option>--state=
</option>.
</para>
128 <xi:include href=
"version-info.xml" xpointer=
"v252"/>
133 <term><command>list-paths
</command> <optional><replaceable>PATTERN
</replaceable>…
</optional></term>
136 <para>List path units currently in memory, ordered by path. If one or more
137 <replaceable>PATTERN
</replaceable>s are specified, only path units matching one of them are shown.
138 Produces output similar to
140 PATH CONDITION UNIT ACTIVATES
141 /run/systemd/ask-password DirectoryNotEmpty systemd-ask-password-plymouth.path systemd-ask-password-plymouth.service
142 /run/systemd/ask-password DirectoryNotEmpty systemd-ask-password-wall.path systemd-ask-password-wall.service
143 /var/cache/cups/org.cups.cupsd PathExists cups.path cups.service
145 3 paths listed.
</programlisting>
148 <para>Also see
<option>--show-types
</option>,
<option>--all
</option>, and
<option>--state=
</option>.
</para>
150 <xi:include href=
"version-info.xml" xpointer=
"v254"/>
155 <term><command>list-sockets
</command> <optional><replaceable>PATTERN
</replaceable>…
</optional></term>
158 <para>List socket units currently in memory, ordered by listening address. If one or more
159 <replaceable>PATTERN
</replaceable>s are specified, only socket units matching one of them are
160 shown. Produces output similar to
162 LISTEN UNIT ACTIVATES
163 /dev/initctl systemd-initctl.socket systemd-initctl.service
165 [::]:
22 sshd.socket sshd.service
166 kobject-uevent
1 systemd-udevd-kernel.socket systemd-udevd.service
168 5 sockets listed.
</programlisting>
169 Note: because the addresses might contains spaces, this output
170 is not suitable for programmatic consumption.
173 <para>Also see
<option>--show-types
</option>,
<option>--all
</option>, and
<option>--state=
</option>.
</para>
175 <xi:include href=
"version-info.xml" xpointer=
"v202"/>
180 <term><command>list-timers
</command> <optional><replaceable>PATTERN
</replaceable>…
</optional></term>
183 <para>List timer units currently in memory, ordered by the time they elapse next. If one or more
184 <replaceable>PATTERN
</replaceable>s are specified, only units matching one of them are shown.
185 Produces output similar to
187 NEXT LEFT LAST PASSED UNIT ACTIVATES
188 - - Thu
2017-
02-
23 13:
40:
29 EST
3 days ago ureadahead-stop.timer ureadahead-stop.service
189 Sun
2017-
02-
26 18:
55:
42 EST
1min
14s left Thu
2017-
02-
23 13:
54:
44 EST
3 days ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
190 Sun
2017-
02-
26 20:
37:
16 EST
1h
42min left Sun
2017-
02-
26 11:
56:
36 EST
6h ago apt-daily.timer apt-daily.service
191 Sun
2017-
02-
26 20:
57:
49 EST
2h
3min left Sun
2017-
02-
26 11:
56:
36 EST
6h ago snapd.refresh.timer snapd.refresh.service
195 <para><emphasis>NEXT
</emphasis> shows the next time the timer will run.
</para>
196 <para><emphasis>LEFT
</emphasis> shows how long till the next time the timer runs.
</para>
197 <para><emphasis>LAST
</emphasis> shows the last time the timer ran.
</para>
198 <para><emphasis>PASSED
</emphasis> shows how long has passed since the timer last ran.
</para>
199 <para><emphasis>UNIT
</emphasis> shows the name of the timer
</para>
200 <para><emphasis>ACTIVATES
</emphasis> shows the name the service the timer activates when it runs.
</para>
202 <para>Also see
<option>--all
</option> and
<option>--state=
</option>.
</para>
204 <xi:include href=
"version-info.xml" xpointer=
"v209"/>
209 <term><command>is-active
<replaceable>PATTERN
</replaceable>…
</command></term>
212 <para>Check whether any of the specified units are active
213 (i.e. running). Returns an exit code
214 <constant>0</constant> if at least one is active, or
215 non-zero otherwise. Unless
<option>--quiet
</option> is
216 specified, this will also print the current unit state to
217 standard output.
</para>
222 <term><command>is-failed
<replaceable>PATTERN
</replaceable>…
</command></term>
225 <para>Check whether any of the specified units are in a
226 "failed" state. Returns an exit code
227 <constant>0</constant> if at least one has failed,
228 non-zero otherwise. Unless
<option>--quiet
</option> is
229 specified, this will also print the current unit state to
230 standard output.
</para>
232 <xi:include href=
"version-info.xml" xpointer=
"v197"/>
237 <term><command>status
</command> <optional><replaceable>PATTERN
</replaceable>…|
<replaceable>PID
</replaceable>…]
</optional></term>
240 <para>Show runtime status information about the whole system or about one or more units followed
241 by most recent log data from the journal. If no positional arguments are specified, and no unit
242 filter is given with
<option>--type=
</option>,
<option>--state=
</option>, or
243 <option>--failed
</option>, shows the status of the whole system. If combined with
244 <option>--all
</option>, follows that with the status of all units. If positional arguments are
245 specified, each positional argument is treated as either a unit name to show, or a glob pattern
246 to show units whose names match that pattern, or a PID to show the unit containing that PID. When
247 <option>--type=
</option>,
<option>--state=
</option>, or
<option>--failed
</option> are used, units
248 are additionally filtered by the TYPE and ACTIVE state.
</para>
250 <para>This function is intended to generate human-readable output. If you are looking for
251 computer-parsable output, use
<command>show
</command> instead. By default, this function only
252 shows
10 lines of output and ellipsizes lines to fit in the terminal window. This can be changed
253 with
<option>--lines
</option> and
<option>--full
</option>, see above. In addition,
254 <command>journalctl --unit=
<replaceable>NAME
</replaceable></command> or
<command>journalctl
255 --user-unit=
<replaceable>NAME
</replaceable></command> use a similar filter for messages and might
256 be more convenient.
</para>
258 <para>Note that this operation only displays
<emphasis>runtime
</emphasis> status, i.e. information about
259 the current invocation of the unit (if it is running) or the most recent invocation (if it is not
260 running anymore, and has not been released from memory). Information about earlier invocations,
261 invocations from previous system boots, or prior invocations that have already been released from
262 memory may be retrieved via
<command>journalctl --unit=
</command>.
</para>
264 <para>systemd implicitly loads units as necessary, so just running the
<command>status
</command>
265 will attempt to load a file. The command is thus not useful for determining if something was
266 already loaded or not. The units may possibly also be quickly unloaded after the operation is
267 completed if there's no reason to keep it in memory thereafter.
</para>
270 <title>Example output from systemctl status
</title>
272 <programlisting>$ systemctl status bluetooth
273 ● bluetooth.service - Bluetooth service
274 Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
275 Active: active (running) since Wed
2017-
01-
04 13:
54:
04 EST;
1 weeks
0 days ago
276 Docs: man:bluetoothd(
8)
277 Main PID:
930 (bluetoothd)
282 CGroup: /system.slice/bluetooth.service
283 └─
930 /usr/lib/bluetooth/bluetoothd
285 Jan
12 10:
46:
45 example.com bluetoothd[
8900]: Not enough free handles to register service
286 Jan
12 10:
46:
45 example.com bluetoothd[
8900]: Current Time Service could not be registered
287 Jan
12 10:
46:
45 example.com bluetoothd[
8900]: gatt-time-server: Input/output error (
5)
290 <para>The dot (
"●") uses color on supported terminals to summarize the unit state at a
291 glance. Along with its color, its shape varies according to its state:
292 <literal>inactive
</literal> or
<literal>maintenance
</literal> is a white circle (
"○"),
293 <literal>active
</literal> is a green dot (
"●"),
<literal>deactivating
</literal> is a white dot,
294 <literal>failed
</literal> or
<literal>error
</literal> is a red cross (
"×"), and
295 <literal>reloading
</literal> is a green clockwise circle arrow (
"↻").
</para>
297 <para>The
"Loaded:" line in the output will show
<literal>loaded
</literal> if the unit has been
298 loaded into memory. Other possible values for
"Loaded:" include:
<literal>error
</literal> if
299 there was a problem loading it,
<literal>not-found
</literal> if no unit file was found for this
300 unit,
<literal>bad-setting
</literal> if an essential unit file setting could not be parsed and
301 <literal>masked
</literal> if the unit file has been masked. Along with showing the path to the
302 unit file, this line will also show the enablement state. Enabled units are included in the
303 dependency network between units, and thus are started at boot or via some other form of
304 activation. See the full table of possible enablement states — including the definition of
305 <literal>masked
</literal> — in the documentation for the
<command>is-enabled
</command> command.
308 <para>The
"Active:" line shows active state. The value is usually
<literal>active
</literal> or
309 <literal>inactive
</literal>. Active could mean started, bound, plugged in, etc depending on the
310 unit type. The unit could also be in process of changing states, reporting a state of
311 <literal>activating
</literal> or
<literal>deactivating
</literal>. A special
312 <literal>failed
</literal> state is entered when the service failed in some way, such as a crash,
313 exiting with an error code or timing out. If the failed state is entered the cause will be logged
314 for later reference.
</para>
321 <term><command>show
</command> <optional><replaceable>PATTERN
</replaceable>…|
<replaceable>JOB
</replaceable>…
</optional></term>
324 <para>Show properties of one or more units, jobs, or the manager itself. If no argument is specified,
325 properties of the manager will be shown. If a unit name is specified, properties of the unit are shown, and
326 if a job ID is specified, properties of the job are shown. By default, empty properties are suppressed. Use
327 <option>--all
</option> to show those too. To select specific properties to show, use
328 <option>--property=
</option>. This command is intended to be used whenever computer-parsable output is
329 required. Use
<command>status
</command> if you are looking for formatted human-readable output.
</para>
331 <para>Many properties shown by
<command>systemctl show
</command> map directly to configuration settings of
332 the system and service manager and its unit files. Note that the properties shown by the command are
333 generally more low-level, normalized versions of the original configuration settings and expose runtime
334 state in addition to configuration. For example, properties shown for service units include the service's
335 current main process identifier as
<literal>MainPID
</literal> (which is runtime state), and time settings
336 are always exposed as properties ending in the
<literal>…USec
</literal> suffix even if a matching
337 configuration options end in
<literal>…Sec
</literal>, because microseconds is the normalized time unit used
338 internally by the system and service manager.
</para>
340 <para>For details about many of these properties, see the documentation of the D-Bus interface
341 backing these properties, see
342 <citerefentry><refentrytitle>org.freedesktop.systemd1
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
347 <term><command>cat
<replaceable>PATTERN
</replaceable>…
</command></term>
350 <para>Show backing files of one or more units. Prints the
351 "fragment" and
"drop-ins" (source files) of units. Each
352 file is preceded by a comment which includes the file
353 name. Note that this shows the contents of the backing files
354 on disk, which may not match the system manager's
355 understanding of these units if any unit files were
356 updated on disk and the
<command>daemon-reload
</command>
357 command wasn't issued since.
</para>
359 <xi:include href=
"version-info.xml" xpointer=
"v209"/>
364 <term><command>help
<replaceable>PATTERN
</replaceable>…|
<replaceable>PID
</replaceable>…
</command></term>
367 <para>Show manual pages for one or more units, if
368 available. If a PID is given, the manual pages for the unit
369 the process belongs to are shown.
</para>
371 <xi:include href=
"version-info.xml" xpointer=
"v185"/>
377 <command>list-dependencies
</command>
378 <optional><replaceable>UNIT
</replaceable>...
</optional>
382 <para>Shows units required and wanted by the specified
383 units. This recursively lists units following the
384 <varname>Requires=
</varname>,
<varname>Requisite=
</varname>,
385 <varname>Wants=
</varname>,
<varname>ConsistsOf=
</varname>,
386 <varname>BindsTo=
</varname>, and
<varname>Upholds=
</varname>
387 dependencies. If no units are specified,
388 <filename>default.target
</filename> is implied.
</para>
390 <para>The units that are shown are additionally filtered by
<option>--type=
</option> and
391 <option>--state=
</option> if those options are specified. Note that we won't be able to
392 use a tree structure in this case, so
<option>--plain
</option> is implied.
</para>
394 <para>By default, only target units are recursively
395 expanded. When
<option>--all
</option> is passed, all other
396 units are recursively expanded as well.
</para>
398 <para>Options
<option>--reverse
</option>,
399 <option>--after
</option>,
<option>--before
</option>
400 may be used to change what types of dependencies
403 <para>Note that this command only lists units currently loaded into memory by the service manager. In
404 particular, this command is not suitable to get a comprehensive list at all reverse dependencies on a
405 specific unit, as it won't list the dependencies declared by units currently not loaded.
</para>
407 <xi:include href=
"version-info.xml" xpointer=
"v198"/>
411 <!-- Commands that modify unit state start here -->
414 <term><command>start
<replaceable>PATTERN
</replaceable>…
</command></term>
417 <para>Start (activate) one or more units specified on the command line.
</para>
419 <para>Note that unit glob patterns expand to names of units currently in memory. Units which are
420 not active and are not in a failed state usually are not in memory, and will not be matched by
421 any pattern. In addition, in case of instantiated units, systemd is often unaware of the instance
422 name until the instance has been started. Therefore, using glob patterns with
423 <command>start
</command> has limited usefulness. Also, secondary alias names of units are not
426 <para>Option
<option>--all
</option> may be used to also operate on inactive units which are
427 referenced by other loaded units. Note that this is not the same as operating on
"all" possible
428 units, because as the previous paragraph describes, such a list is ill-defined. Nevertheless,
429 <command>systemctl start --all
<replaceable>GLOB
</replaceable></command> may be useful if all the
430 units that should match the pattern are pulled in by some target which is known to be loaded.
435 <term><command>stop
<replaceable>PATTERN
</replaceable>…
</command></term>
438 <para>Stop (deactivate) one or more units specified on the command line.
</para>
440 <para>This command will fail if the unit does not exist or if stopping of the unit is prohibited (see
441 <varname>RefuseManualStop=
</varname> in
442 <citerefentry><refentrytitle>systemd.unit
</refentrytitle><manvolnum>5</manvolnum></citerefentry>).
443 It will
<emphasis>not
</emphasis> fail if any of the commands configured to stop the unit
444 (
<varname>ExecStop=
</varname>, etc.) fail, because the manager will still forcibly terminate the
447 <para>If a unit that gets stopped can still be triggered by other units, a warning containing
448 the names of the triggering units is shown.
<option>--no-warn
</option> can be used to suppress
453 <term><command>reload
<replaceable>PATTERN
</replaceable>…
</command></term>
456 <para>Asks all units listed on the command line to reload
457 their configuration. Note that this will reload the
458 service-specific configuration, not the unit configuration
459 file of systemd. If you want systemd to reload the
460 configuration file of a unit, use the
461 <command>daemon-reload
</command> command. In other words:
462 for the example case of Apache, this will reload Apache's
463 <filename>httpd.conf
</filename> in the web server, not the
464 <filename>apache.service
</filename> systemd unit
467 <para>This command should not be confused with the
468 <command>daemon-reload
</command> command.
</para>
473 <term><command>restart
<replaceable>PATTERN
</replaceable>…
</command></term>
476 <para>Stop and then start one or more units specified on the command line. If the units are not running
477 yet, they will be started.
</para>
479 <para>Note that restarting a unit with this command does not necessarily flush out all of the unit's
480 resources before it is started again. For example, the per-service file descriptor storage facility (see
481 <varname>FileDescriptorStoreMax=
</varname> in
482 <citerefentry><refentrytitle>systemd.service
</refentrytitle><manvolnum>5</manvolnum></citerefentry>) will
483 remain intact as long as the unit has a job pending, and is only cleared when the unit is fully stopped and
484 no jobs are pending anymore. If it is intended that the file descriptor store is flushed out, too, during a
485 restart operation an explicit
<command>systemctl stop
</command> command followed by
<command>systemctl
486 start
</command> should be issued.
</para>
490 <term><command>try-restart
<replaceable>PATTERN
</replaceable>…
</command></term>
493 <para>Stop and then start one or more units specified on the
494 command line if the units are running. This does nothing
495 if units are not running.
</para>
496 <!-- Note that we don't document condrestart here, as that is just compatibility support, and we generally
497 don't document that. -->
501 <term><command>reload-or-restart
<replaceable>PATTERN
</replaceable>…
</command></term>
504 <para>Reload one or more units if they support it. If not, stop and then start them instead. If the units
505 are not running yet, they will be started.
</para>
509 <term><command>try-reload-or-restart
<replaceable>PATTERN
</replaceable>…
</command></term>
512 <para>Reload one or more units if they support it. If not, stop and then start them instead. This does
513 nothing if the units are not running.
</para>
514 <!-- Note that we don't document force-reload here, as that is just compatibility support, and we generally
515 don't document that. -->
517 <xi:include href=
"version-info.xml" xpointer=
"v229"/>
521 <term><command>isolate
<replaceable>UNIT
</replaceable></command></term>
524 <para>Start the unit specified on the command line and its dependencies
525 and stop all others, unless they have
526 <option>IgnoreOnIsolate=yes
</option> (see
527 <citerefentry><refentrytitle>systemd.unit
</refentrytitle><manvolnum>5</manvolnum></citerefentry>).
528 If a unit name with no extension is given, an extension of
529 <literal>.target
</literal> will be assumed.
</para>
531 <para>This command is dangerous, since it will immediately stop processes that are not enabled in
532 the new target, possibly including the graphical environment or terminal you are currently using.
535 <para>Note that this operation is allowed only on units where
536 <option>AllowIsolate=
</option> is enabled. See
537 <citerefentry><refentrytitle>systemd.unit
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
542 <term><command>kill
<replaceable>PATTERN
</replaceable>…
</command></term>
545 <para>Send a UNIX process signal to one or more processes of the unit. Use
546 <option>--kill-whom=
</option> to select which process to send the signal to. Use
547 <option>--signal=
</option> to select the signal to send. Combine with
548 <option>--kill-value=
</option> to enqueue a POSIX Realtime Signal with an associated
553 <term><command>clean
<replaceable>PATTERN
</replaceable>…
</command></term>
556 <para>Remove the configuration, state, cache, logs or runtime data of the specified units. Use
557 <option>--what=
</option> to select which kind of resource to remove. For service units this may
558 be used to remove the directories configured with
<varname>ConfigurationDirectory=
</varname>,
559 <varname>StateDirectory=
</varname>,
<varname>CacheDirectory=
</varname>,
560 <varname>LogsDirectory=
</varname> and
<varname>RuntimeDirectory=
</varname>, see
561 <citerefentry><refentrytitle>systemd.exec
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
562 for details. It may also be used to clear the file descriptor store as enabled via
563 <varname>FileDescriptorStoreMax=
</varname>, see
564 <citerefentry><refentrytitle>systemd.service
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
565 for details. For timer units this may be used to clear out the persistent timestamp data if
566 <varname>Persistent=
</varname> is used and
<option>--what=state
</option> is selected, see
567 <citerefentry><refentrytitle>systemd.timer
</refentrytitle><manvolnum>5</manvolnum></citerefentry>. This
568 command only applies to units that use either of these settings. If
<option>--what=
</option> is
569 not specified, the cache and runtime data as well as the file descriptor store are removed (as
570 these three types of resources are generally redundant and reproducible on the next invocation of
571 the unit). Note that the specified units must be stopped to invoke this operation.
</para>
573 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
577 <term><command>freeze
<replaceable>PATTERN
</replaceable>…
</command></term>
580 <para>Freeze one or more units specified on the
581 command line using cgroup freezer
</para>
583 <para>Freezing the unit will cause all processes contained within the cgroup corresponding to the unit
584 to be suspended. Being suspended means that unit's processes won't be scheduled to run on CPU until thawed.
585 Note that this command is supported only on systems that use unified cgroup hierarchy. Unit is automatically
586 thawed just before we execute a job against the unit, e.g. before the unit is stopped.
</para>
588 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
592 <term><command>thaw
<replaceable>PATTERN
</replaceable>…
</command></term>
595 <para>Thaw (unfreeze) one or more units specified on the
598 <para>This is the inverse operation to the
<command>freeze
</command> command and resumes the execution of
599 processes in the unit's cgroup.
</para>
601 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
605 <term><command>set-property
<replaceable>UNIT
</replaceable> <replaceable>PROPERTY
</replaceable>=
<replaceable>VALUE
</replaceable>…
</command></term>
608 <para>Set the specified unit properties at runtime where
609 this is supported. This allows changing configuration
610 parameter properties such as resource control settings at
611 runtime. Not all properties may be changed at runtime, but
612 many resource control settings (primarily those in
613 <citerefentry><refentrytitle>systemd.resource-control
</refentrytitle><manvolnum>5</manvolnum></citerefentry>)
614 may. The changes are applied immediately, and stored on disk
615 for future boots, unless
<option>--runtime
</option> is
616 passed, in which case the settings only apply until the
617 next reboot. The syntax of the property assignment follows
618 closely the syntax of assignments in unit files.
</para>
620 <para>Example:
<command>systemctl set-property foobar.service CPUWeight=
200</command></para>
622 <para>If the specified unit appears to be inactive, the
623 changes will be only stored on disk as described
624 previously hence they will be effective when the unit will
627 <para>Note that this command allows changing multiple properties at the same time, which is
628 preferable over setting them individually.
</para>
630 <para>Example:
<command>systemctl set-property foobar.service CPUWeight=
200 MemoryMax=
2G IPAccounting=yes
</command></para>
632 <para>Like with unit file configuration settings, assigning an empty setting usually resets a
633 property to its defaults.
</para>
635 <para>Example:
<command>systemctl set-property avahi-daemon.service IPAddressDeny=
</command></para>
637 <xi:include href=
"version-info.xml" xpointer=
"v206"/>
643 <command>bind
</command>
644 <replaceable>UNIT
</replaceable>
645 <replaceable>PATH
</replaceable>
646 [
<replaceable>PATH
</replaceable>]
649 <listitem><para>Bind-mounts a file or directory from the host into the specified unit's mount
650 namespace. The first path argument is the source file or directory on the host, the second path
651 argument is the destination file or directory in the unit's mount namespace. When the latter is
652 omitted, the destination path in the unit's mount namespace is the same as the source path on the
653 host. When combined with the
<option>--read-only
</option> switch, a ready-only bind mount is
654 created. When combined with the
<option>--mkdir
</option> switch, the destination path is first
655 created before the mount is applied.
</para>
657 <para>Note that this option is currently only supported for units that run within a mount namespace
658 (e.g.: with
<option>RootImage=
</option>,
<option>PrivateMounts=
</option>, etc.). This command
659 supports bind-mounting directories, regular files, device nodes,
<constant>AF_UNIX
</constant>
660 socket nodes, as well as FIFOs. The bind mount is ephemeral, and it is undone as soon as the
661 current unit process exists. Note that the namespace mentioned here, where the bind mount will be
662 added to, is the one where the main service process runs. Other processes (those exececuted by
663 <option>ExecReload=
</option>,
<option>ExecStartPre=
</option>, etc.) run in distinct namespaces.
666 <para>If supported by the kernel, any prior mount on the selected target will be replaced by the
667 new mount. If not supported, any prior mount will be over-mounted, but remain pinned and
670 <xi:include href=
"version-info.xml" xpointer=
"v248"/></listitem>
675 <command>mount-image
</command>
676 <replaceable>UNIT
</replaceable>
677 <replaceable>IMAGE
</replaceable>
678 [
<replaceable>PATH
</replaceable>
679 [
<replaceable>PARTITION_NAME
</replaceable>:
<replaceable>MOUNT_OPTIONS
</replaceable>]]
682 <listitem><para>Mounts an image from the host into the specified unit's mount namespace. The first
683 path argument is the source image on the host, the second path argument is the destination
684 directory in the unit's mount namespace (i.e. inside
685 <option>RootImage=
</option>/
<option>RootDirectory=
</option>). The following argument, if any, is
686 interpreted as a colon-separated tuple of partition name and comma-separated list of mount options
687 for that partition. The format is the same as the service
<option>MountImages=
</option>
688 setting. When combined with the
<option>--read-only
</option> switch, a ready-only mount is
689 created. When combined with the
<option>--mkdir
</option> switch, the destination path is first
690 created before the mount is applied.
</para>
692 <para>Note that this option is currently only supported for units that run within a mount namespace
693 (i.e. with
<option>RootImage=
</option>,
<option>PrivateMounts=
</option>, etc.). Note that the
694 namespace mentioned here where the image mount will be added to, is the one where the main service
695 process runs. Note that the namespace mentioned here, where the bind mount will be
696 added to, is the one where the main service process runs. Other processes (those exececuted by
697 <option>ExecReload=
</option>,
<option>ExecStartPre=
</option>, etc.) run in distinct namespaces.
700 <para>If supported by the kernel, any prior mount on the selected target will be replaced by the
701 new mount. If not supported, any prior mount will be over-mounted, but remain pinned and
705 <programlisting>systemctl mount-image foo.service /tmp/img.raw /var/lib/image root:ro,nosuid
</programlisting>
706 <programlisting>systemctl mount-image --mkdir bar.service /tmp/img.raw /var/lib/baz/img
</programlisting>
709 <xi:include href=
"version-info.xml" xpointer=
"v248"/></listitem>
713 <term><command>service-log-level
</command> <replaceable>SERVICE
</replaceable> [
<replaceable>LEVEL
</replaceable>]
</term>
715 <listitem><para>If the
<replaceable>LEVEL
</replaceable> argument is not given, print the current
716 log level as reported by service
<replaceable>SERVICE
</replaceable>.
</para>
718 <para>If the optional argument
<replaceable>LEVEL
</replaceable> is provided, then change the
719 current log level of the service to
<replaceable>LEVEL
</replaceable>. The log level should be a
720 typical syslog log level, i.e. a value in the range
0…
7 or one of the strings
721 <constant>emerg
</constant>,
<constant>alert
</constant>,
<constant>crit
</constant>,
722 <constant>err
</constant>,
<constant>warning
</constant>,
<constant>notice
</constant>,
723 <constant>info
</constant>,
<constant>debug
</constant>; see
<citerefentry
724 project='man-pages'
><refentrytitle>syslog
</refentrytitle><manvolnum>3</manvolnum></citerefentry>
727 <para>The service must have the appropriate
728 <varname>BusName=
<replaceable>destination
</replaceable></varname> property and also implement the
730 <citerefentry><refentrytitle>org.freedesktop.LogControl1
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
731 interface. (
<filename>systemctl
</filename> will use the generic D-Bus protocol to access the
732 <interfacename>org.freedesktop.LogControl1.LogLevel
</interfacename> interface for the D-Bus name
733 <replaceable>destination
</replaceable>.)
</para>
735 <xi:include href=
"version-info.xml" xpointer=
"v247"/></listitem>
739 <term><command>service-log-target
</command> <replaceable>SERVICE
</replaceable> [
<replaceable>TARGET
</replaceable>]
</term>
741 <listitem><para>If the
<replaceable>TARGET
</replaceable> argument is not given, print the current
742 log target as reported by service
<replaceable>SERVICE
</replaceable>.
</para>
744 <para>If the optional argument
<replaceable>TARGET
</replaceable> is provided, then change the
745 current log target of the service to
<replaceable>TARGET
</replaceable>. The log target should be
746 one of the strings
<constant>console
</constant> (for log output to the service's standard error
747 stream),
<constant>kmsg
</constant> (for log output to the kernel log buffer),
748 <constant>journal
</constant> (for log output to
749 <citerefentry><refentrytitle>systemd-journald.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>
750 using the native journal protocol),
<constant>syslog
</constant> (for log output to the classic
751 syslog socket
<filename>/dev/log
</filename>),
<constant>null
</constant> (for no log output
752 whatsoever) or
<constant>auto
</constant> (for an automatically determined choice, typically
753 equivalent to
<constant>console
</constant> if the service is invoked interactively, and
754 <constant>journal
</constant> or
<constant>syslog
</constant> otherwise).
</para>
756 <para>For most services, only a small subset of log targets make sense. In particular, most
757 "normal" services should only implement
<constant>console
</constant>,
<constant>journal
</constant>,
758 and
<constant>null
</constant>. Anything else is only appropriate for low-level services that
759 are active in very early boot before proper logging is established.
</para>
761 <para>The service must have the appropriate
762 <varname>BusName=
<replaceable>destination
</replaceable></varname> property and also implement the
764 <citerefentry><refentrytitle>org.freedesktop.LogControl1
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
765 interface. (
<filename>systemctl
</filename> will use the generic D-Bus protocol to access the
766 <interfacename>org.freedesktop.LogControl1.LogLevel
</interfacename> interface for the D-Bus name
767 <replaceable>destination
</replaceable>.)
</para>
769 <xi:include href=
"version-info.xml" xpointer=
"v247"/></listitem>
773 <term><command>reset-failed [
<replaceable>PATTERN
</replaceable>…]
</command></term>
776 <para>Reset the
<literal>failed
</literal> state of the specified units, or if no unit name is passed, reset
777 the state of all units. When a unit fails in some way (i.e. process exiting with non-zero error code,
778 terminating abnormally or timing out), it will automatically enter the
<literal>failed
</literal> state and
779 its exit code and status is recorded for introspection by the administrator until the service is
780 stopped/re-started or reset with this command.
</para>
782 <para>In addition to resetting the
<literal>failed
</literal> state of a unit it also resets various other
783 per-unit properties: the start rate limit counter of all unit types is reset to zero, as is the restart
784 counter of service units. Thus, if a unit's start limit (as configured with
785 <varname>StartLimitIntervalSec=
</varname>/
<varname>StartLimitBurst=
</varname>) is hit and the unit refuses
786 to be started again, use this command to make it startable again.
</para>
791 <term><command>whoami [
<replaceable>PID
</replaceable>…]
</command></term>
793 <listitem><para>Returns the units the processes referenced by the given PIDs belong to (one per
794 line). If no PID is specified returns the unit the
<command>systemctl
</command> command is invoked
797 <xi:include href=
"version-info.xml" xpointer=
"v254"/></listitem>
804 <title>Unit File Commands
</title>
808 <term><command>list-unit-files
</command> <optional><replaceable>PATTERN…
</replaceable></optional></term>
811 <para>List unit files installed on the system, in combination with their enablement state (as
812 reported by
<command>is-enabled
</command>). If one or more
<replaceable>PATTERN
</replaceable>s
813 are specified, only unit files whose name matches one of them are shown (patterns matching unit
814 file system paths are not supported).
</para>
816 <para>Unlike
<command>list-units
</command> this command will list template units in addition to
817 explicitly instantiated units.
</para>
819 <xi:include href=
"version-info.xml" xpointer=
"v233"/>
824 <term><command>enable
<replaceable>UNIT
</replaceable>…
</command></term>
825 <term><command>enable
<replaceable>PATH
</replaceable>…
</command></term>
828 <para>Enable one or more units or unit instances. This will create a set of symlinks, as encoded in the
829 [Install] sections of the indicated unit files. After the symlinks have been created,
830 the system manager configuration is reloaded (in a way equivalent to
<command>daemon-reload
</command>), in
831 order to ensure the changes are taken into account immediately. Note that this does
832 <emphasis>not
</emphasis> have the effect of also starting any of the units being enabled. If this is
833 desired, combine this command with the
<option>--now
</option> switch, or invoke
<command>start
</command>
834 with appropriate arguments later. Note that in case of unit instance enablement (i.e. enablement of units of
835 the form
<filename>foo@bar.service
</filename>), symlinks named the same as instances are created in the
836 unit configuration directory, however they point to the single template unit file they are instantiated
839 <para>This command expects either valid unit names (in which case various unit file directories are
840 automatically searched for unit files with appropriate names), or absolute paths to unit files (in which
841 case these files are read directly). If a specified unit file is located outside of the usual unit file
842 directories, an additional symlink is created, linking it into the unit configuration path, thus ensuring
843 it is found when requested by commands such as
<command>start
</command>. The file system where the linked
844 unit files are located must be accessible when systemd is started (e.g. anything underneath
845 <filename>/home/
</filename> or
<filename>/var/
</filename> is not allowed, unless those directories are
846 located on the root file system).
</para>
848 <para>This command will print the file system operations executed. This output may be suppressed by passing
849 <option>--quiet
</option>.
852 <para>Note that this operation creates only the symlinks suggested in the [Install]
853 section of the unit files. While this command is the recommended way to manipulate the unit configuration
854 directory, the administrator is free to make additional changes manually by placing or removing symlinks
855 below this directory. This is particularly useful to create configurations that deviate from the suggested
856 default installation. In this case, the administrator must make sure to invoke
857 <command>daemon-reload
</command> manually as necessary, in order to ensure the changes are taken into
861 <para>When using this operation on units without install information, a warning about it is shown.
862 <option>--no-warn
</option> can be used to suppress the warning.
</para>
864 <para>Enabling units should not be confused with starting (activating) units, as done by the
865 <command>start
</command> command. Enabling and starting units is orthogonal: units may be enabled without
866 being started and started without being enabled. Enabling simply hooks the unit into various suggested
867 places (for example, so that the unit is automatically started on boot or when a particular kind of
868 hardware is plugged in). Starting actually spawns the daemon process (in case of service units), or binds
869 the socket (in case of socket units), and so on.
</para>
871 <para>Depending on whether
<option>--system
</option>,
<option>--user
</option>,
<option>--runtime
</option>,
872 or
<option>--global
</option> is specified, this enables the unit for the system, for the calling user only,
873 for only this boot of the system, or for all future logins of all users. Note that in the last case, no
874 systemd daemon configuration is reloaded.
</para>
876 <para>Using
<command>enable
</command> on masked units is not supported and results in an error.
</para>
881 <term><command>disable
<replaceable>UNIT
</replaceable>…
</command></term>
884 <para>Disables one or more units. This removes all symlinks to the unit files backing the specified units
885 from the unit configuration directory, and hence undoes any changes made by
<command>enable
</command> or
886 <command>link
</command>. Note that this removes
<emphasis>all
</emphasis> symlinks to matching unit files,
887 including manually created symlinks, and not just those actually created by
<command>enable
</command> or
888 <command>link
</command>. Note that while
<command>disable
</command> undoes the effect of
889 <command>enable
</command>, the two commands are otherwise not symmetric, as
<command>disable
</command> may
890 remove more symlinks than a prior
<command>enable
</command> invocation of the same unit created.
</para>
892 <para>This command expects valid unit names only, it does not accept paths to unit files.
</para>
894 <para>In addition to the units specified as arguments, all units are disabled that are listed in the
895 <varname>Also=
</varname> setting contained in the [Install] section of any of the unit
896 files being operated on.
</para>
898 <para>This command implicitly reloads the system manager configuration after completing the operation. Note
899 that this command does not implicitly stop the units that are being disabled. If this is desired, either
900 combine this command with the
<option>--now
</option> switch, or invoke the
<command>stop
</command> command
901 with appropriate arguments later.
</para>
903 <para>This command will print information about the file system operations (symlink removals)
904 executed. This output may be suppressed by passing
<option>--quiet
</option>.
907 <para>If a unit gets disabled but its triggering units are still active, a warning containing
908 the names of the triggering units is shown.
<option>--no-warn
</option> can be used to suppress
911 <para>When this command is used with
<option>--user
</option>, the units being operated on might
912 still be enabled in global scope, and thus get started automatically even after a successful
913 disablement in user scope. In this case, a warning about it is shown, which can be suppressed
914 using
<option>--no-warn
</option>.
</para>
916 <para>This command honors
<option>--system
</option>,
<option>--user
</option>,
<option>--runtime
</option>,
917 <option>--global
</option> and
<option>--no-warn
</option> in a similar way as
<command>enable
</command>.
</para>
919 <xi:include href=
"version-info.xml" xpointer=
"v238"/>
924 <term><command>reenable
<replaceable>UNIT
</replaceable>…
</command></term>
927 <para>Reenable one or more units, as specified on the command line. This is a combination of
928 <command>disable
</command> and
<command>enable
</command> and is useful to reset the symlinks a unit file is
929 enabled with to the defaults configured in its [Install] section. This command expects
930 a unit name only, it does not accept paths to unit files.
</para>
932 <xi:include href=
"version-info.xml" xpointer=
"v238"/>
937 <term><command>preset
<replaceable>UNIT
</replaceable>…
</command></term>
940 <para>Reset the enable/disable status one or more unit files, as specified on
941 the command line, to the defaults configured in the preset policy files. This
942 has the same effect as
<command>disable
</command> or
943 <command>enable
</command>, depending how the unit is listed in the preset
946 <para>Use
<option>--preset-mode=
</option> to control whether units shall be
947 enabled and disabled, or only enabled, or only disabled.
</para>
949 <para>If the unit carries no install information, it will be silently ignored
950 by this command.
<replaceable>UNIT
</replaceable> must be the real unit name,
951 any alias names are ignored silently.
</para>
953 <para>For more information on the preset policy format, see
954 <citerefentry><refentrytitle>systemd.preset
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
957 <xi:include href=
"version-info.xml" xpointer=
"v238"/>
962 <term><command>preset-all
</command></term>
965 <para>Resets all installed unit files to the defaults
966 configured in the preset policy file (see above).
</para>
968 <para>Use
<option>--preset-mode=
</option> to control
969 whether units shall be enabled and disabled, or only
970 enabled, or only disabled.
</para>
972 <xi:include href=
"version-info.xml" xpointer=
"v215"/>
977 <term><command>is-enabled
<replaceable>UNIT
</replaceable>…
</command></term>
980 <para>Checks whether any of the specified unit files are
981 enabled (as with
<command>enable
</command>). Returns an
982 exit code of
0 if at least one is enabled, non-zero
983 otherwise. Prints the current enable status (see table).
984 To suppress this output, use
<option>--quiet
</option>.
985 To show installation targets, use
<option>--full
</option>.
990 <command>is-enabled
</command> output
997 <entry>Description
</entry>
998 <entry>Exit Code
</entry>
1003 <entry><literal>enabled
</literal></entry>
1004 <entry morerows='
1'
>Enabled via
<filename>.wants/
</filename>,
<filename>.requires/
</filename> or
<varname>Alias=
</varname> symlinks (permanently in
<filename>/etc/systemd/system/
</filename>, or transiently in
<filename>/run/systemd/system/
</filename>).
</entry>
1005 <entry morerows='
1'
>0</entry>
1008 <entry><literal>enabled-runtime
</literal></entry>
1011 <entry><literal>linked
</literal></entry>
1012 <entry morerows='
1'
>Made available through one or more symlinks to the unit file (permanently in
<filename>/etc/systemd/system/
</filename> or transiently in
<filename>/run/systemd/system/
</filename>), even though the unit file might reside outside of the unit file search path.
</entry>
1013 <entry morerows='
1'
>> 0</entry>
1016 <entry><literal>linked-runtime
</literal></entry>
1019 <entry><literal>alias
</literal></entry>
1020 <entry>The name is an alias (symlink to another unit file).
</entry>
1024 <entry><literal>masked
</literal></entry>
1025 <entry morerows='
1'
>Completely disabled, so that any start operation on it fails (permanently in
<filename>/etc/systemd/system/
</filename> or transiently in
<filename>/run/systemd/systemd/
</filename>).
</entry>
1026 <entry morerows='
1'
>> 0</entry>
1029 <entry><literal>masked-runtime
</literal></entry>
1032 <entry><literal>static
</literal></entry>
1033 <entry>The unit file is not enabled, and has no provisions for enabling in the [Install] unit file section.
</entry>
1037 <entry><literal>indirect
</literal></entry>
1038 <entry>The unit file itself is not enabled, but it has a non-empty
<varname>Also=
</varname> setting in the [Install] unit file section, listing other unit files that might be enabled, or it has an alias under a different name through a symlink that is not specified in
<varname>Also=
</varname>. For template unit files, an instance different than the one specified in
<varname>DefaultInstance=
</varname> is enabled.
</entry>
1042 <entry><literal>disabled
</literal></entry>
1043 <entry>The unit file is not enabled, but contains an [Install] section with installation instructions.
</entry>
1044 <entry>> 0</entry>
1047 <entry><literal>generated
</literal></entry>
1048 <entry>The unit file was generated dynamically via a generator tool. See
<citerefentry><refentrytitle>systemd.generator
</refentrytitle><manvolnum>7</manvolnum></citerefentry>. Generated unit files may not be enabled, they are enabled implicitly by their generator.
</entry>
1052 <entry><literal>transient
</literal></entry>
1053 <entry>The unit file has been created dynamically with the runtime API. Transient units may not be enabled.
</entry>
1057 <entry><literal>bad
</literal></entry>
1058 <entry>The unit file is invalid or another error occurred. Note that
<command>is-enabled
</command> will not actually return this state, but print an error message instead. However the unit file listing printed by
<command>list-unit-files
</command> might show it.
</entry>
1059 <entry>> 0</entry>
1062 <entry><literal>not-found
</literal></entry>
1063 <entry>The unit file doesn't exist.
</entry>
1070 <xi:include href=
"version-info.xml" xpointer=
"v238"/>
1076 <term><command>mask
<replaceable>UNIT
</replaceable>…
</command></term>
1079 <para>Mask one or more units, as specified on the command line. This will link these unit files
1080 to
<filename>/dev/null
</filename>, making it impossible to start them. This is a stronger version
1081 of
<command>disable
</command>, since it prohibits all kinds of activation of the unit, including
1082 enablement and manual activation. Use this option with care. This honors the
1083 <option>--runtime
</option> option to only mask temporarily until the next reboot of the
1084 system. The
<option>--now
</option> option may be used to ensure that the units are also
1085 stopped. This command expects valid unit names only, it does not accept unit file paths.
</para>
1087 <para>Note that this will create a symlink under the unit's name in
1088 <filename>/etc/systemd/system/
</filename> (in case
<option>--runtime
</option> is not specified)
1089 or
<filename>/run/systemd/system/
</filename> (in case
<option>--runtime
</option> is
1090 specified). If a matching unit file already exists under these directories this operation will
1091 hence fail. This means that the operation is primarily useful to mask units shipped by the vendor
1092 (as those are shipped in
<filename>/usr/lib/systemd/system/
</filename> and not the aforementioned
1093 two directories), but typically doesn't work for units created locally (as those are typically
1094 placed precisely in the two aforementioned directories). Similar restrictions apply for
1095 <option>--user
</option> mode, in which case the directories are below the user's home directory
1098 <para>If a unit gets masked but its triggering units are still active, a warning containing
1099 the names of the triggering units is shown.
<option>--no-warn
</option> can be used to suppress
1102 <xi:include href=
"version-info.xml" xpointer=
"v238"/>
1107 <term><command>unmask
<replaceable>UNIT
</replaceable>…
</command></term>
1110 <para>Unmask one or more unit files, as specified on the command line. This will undo the effect of
1111 <command>mask
</command>. This command expects valid unit names only, it does not accept unit file
1114 <xi:include href=
"version-info.xml" xpointer=
"v238"/>
1119 <term><command>link
<replaceable>PATH
</replaceable>…
</command></term>
1122 <para>Link a unit file that is not in the unit file search path into the unit file search path. This
1123 command expects an absolute path to a unit file. The effect of this may be undone with
1124 <command>disable
</command>. The effect of this command is that a unit file is made available for commands
1125 such as
<command>start
</command>, even though it is not installed directly in the unit search path. The
1126 file system where the linked unit files are located must be accessible when systemd is started
1127 (e.g. anything underneath
<filename>/home/
</filename> or
<filename>/var/
</filename> is not allowed, unless
1128 those directories are located on the root file system).
</para>
1130 <xi:include href=
"version-info.xml" xpointer=
"v233"/>
1135 <term><command>revert
<replaceable>UNIT
</replaceable>…
</command></term>
1138 <para>Revert one or more unit files to their vendor versions. This command removes drop-in configuration
1139 files that modify the specified units, as well as any user-configured unit file that overrides a matching
1140 vendor supplied unit file. Specifically, for a unit
<literal>foo.service
</literal> the matching directories
1141 <literal>foo.service.d/
</literal> with all their contained files are removed, both below the persistent and
1142 runtime configuration directories (i.e. below
<filename>/etc/systemd/system
</filename> and
1143 <filename>/run/systemd/system
</filename>); if the unit file has a vendor-supplied version (i.e. a unit file
1144 located below
<filename>/usr/
</filename>) any matching persistent or runtime unit file that overrides it is
1145 removed, too. Note that if a unit file has no vendor-supplied version (i.e. is only defined below
1146 <filename>/etc/systemd/system
</filename> or
<filename>/run/systemd/system
</filename>, but not in a unit
1147 file stored below
<filename>/usr/
</filename>), then it is not removed. Also, if a unit is masked, it is
1150 <para>Effectively, this command may be used to undo all changes made with
<command>systemctl
1151 edit
</command>,
<command>systemctl set-property
</command> and
<command>systemctl mask
</command> and puts
1152 the original unit file with its settings back in effect.
</para>
1154 <xi:include href=
"version-info.xml" xpointer=
"v230"/>
1159 <term><command>add-wants
<replaceable>TARGET
</replaceable>
1160 <replaceable>UNIT
</replaceable>…
</command></term>
1161 <term><command>add-requires
<replaceable>TARGET
</replaceable>
1162 <replaceable>UNIT
</replaceable>…
</command></term>
1165 <para>Adds
<literal>Wants=
</literal> or
<literal>Requires=
</literal>
1166 dependencies, respectively, to the specified
1167 <replaceable>TARGET
</replaceable> for one or more units.
</para>
1169 <para>This command honors
<option>--system
</option>,
1170 <option>--user
</option>,
<option>--runtime
</option> and
1171 <option>--global
</option> in a way similar to
1172 <command>enable
</command>.
</para>
1174 <xi:include href=
"version-info.xml" xpointer=
"v217"/>
1180 <term><command>edit
<replaceable>UNIT
</replaceable>…
</command></term>
1183 <para>Edit a drop-in snippet or a whole replacement file if
1184 <option>--full
</option> is specified, to extend or override the
1185 specified unit.
</para>
1187 <para>Depending on whether
<option>--system
</option> (the default),
1188 <option>--user
</option>, or
<option>--global
</option> is specified,
1189 this command creates a drop-in file for each unit either for the system,
1190 for the calling user, or for all futures logins of all users. Then,
1191 the editor (see the
"Environment" section below) is invoked on
1192 temporary files which will be written to the real location if the
1193 editor exits successfully.
</para>
1195 <para>If
<option>--drop-in=
</option> is specified, the given drop-in file name
1196 will be used instead of the default
<filename>override.conf
</filename>.
</para>
1198 <para>If
<option>--full
</option> is specified, this will copy the
1199 original units instead of creating drop-in files.
</para>
1201 <para>If
<option>--force
</option> is specified and any units do
1202 not already exist, new unit files will be opened for editing.
</para>
1204 <para>If
<option>--runtime
</option> is specified, the changes will
1205 be made temporarily in
<filename>/run/
</filename> and they will be
1206 lost on the next reboot.
</para>
1208 <para>If the temporary file is empty upon exit, the modification of
1209 the related unit is canceled.
</para>
1211 <para>After the units have been edited, systemd configuration is
1212 reloaded (in a way that is equivalent to
<command>daemon-reload
</command>).
1215 <para>Note that this command cannot be used to remotely edit units
1216 and that you cannot temporarily edit units which are in
1217 <filename>/etc/
</filename>, since they take precedence over
1218 <filename>/run/
</filename>.
</para>
1220 <xi:include href=
"version-info.xml" xpointer=
"v218"/>
1225 <term><command>get-default
</command></term>
1228 <para>Return the default target to boot into. This returns
1229 the target unit name
<filename>default.target
</filename>
1230 is aliased (symlinked) to.
</para>
1232 <xi:include href=
"version-info.xml" xpointer=
"v205"/>
1237 <term><command>set-default
<replaceable>TARGET
</replaceable></command></term>
1240 <para>Set the default target to boot into. This sets
1241 (symlinks) the
<filename>default.target
</filename> alias
1242 to the given target unit.
</para>
1244 <xi:include href=
"version-info.xml" xpointer=
"v205"/>
1252 <title>Machine Commands
</title>
1256 <term><command>list-machines
</command> <optional><replaceable>PATTERN
</replaceable>…
</optional></term>
1259 <para>List the host and all running local containers with
1260 their state. If one or more
1261 <replaceable>PATTERN
</replaceable>s are specified, only
1262 containers matching one of them are shown.
1265 <xi:include href=
"version-info.xml" xpointer=
"v212"/>
1272 <title>Job Commands
</title>
1276 <term><command>list-jobs
<optional><replaceable>PATTERN…
</replaceable></optional></command></term>
1279 <para>List jobs that are in progress. If one or more
1280 <replaceable>PATTERN
</replaceable>s are specified, only
1281 jobs for units matching one of them are shown.
</para>
1283 <para>When combined with
<option>--after
</option> or
<option>--before
</option> the list is augmented with
1284 information on which other job each job is waiting for, and which other jobs are waiting for it, see
1287 <xi:include href=
"version-info.xml" xpointer=
"v233"/>
1291 <term><command>cancel
<optional><replaceable>JOB
</replaceable>…
</optional></command></term>
1294 <para>Cancel one or more jobs specified on the command line
1295 by their numeric job IDs. If no job ID is specified, cancel
1296 all pending jobs.
</para>
1298 <xi:include href=
"version-info.xml" xpointer=
"v233"/>
1305 <title>Environment Commands
</title>
1307 <para><command>systemd
</command> supports an environment block that is passed to processes the manager
1308 spawns. The names of the variables can contain ASCII letters, digits, and the underscore
1309 character. Variable names cannot be empty or start with a digit. In variable values, most characters
1310 are allowed, but the whole sequence must be valid UTF-
8. (Note that control characters like newline
1311 (
<constant>NL
</constant>), tab (
<constant>TAB
</constant>), or the escape character
1312 (
<constant>ESC
</constant>),
<emphasis>are
</emphasis> valid ASCII and thus valid UTF-
8). The total
1313 length of the environment block is limited to
<constant>_SC_ARG_MAX
</constant> value defined by
1314 <citerefentry project='man-pages'
><refentrytitle>sysconf
</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
1319 <term><command>show-environment
</command></term>
1322 <para>Dump the systemd manager environment block. This is the environment
1323 block that is passed to all processes the manager spawns. The environment
1324 block will be dumped in straightforward form suitable for sourcing into
1325 most shells. If no special characters or whitespace is present in the variable
1326 values, no escaping is performed, and the assignments have the form
1327 <literal>VARIABLE=value
</literal>. If whitespace or characters which have
1328 special meaning to the shell are present, dollar-single-quote escaping is
1329 used, and assignments have the form
<literal>VARIABLE=$'value'
</literal>.
1330 This syntax is known to be supported by
1331 <citerefentry project='die-net'
><refentrytitle>bash
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
1332 <citerefentry project='die-net'
><refentrytitle>zsh
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
1333 <citerefentry project='die-net'
><refentrytitle>ksh
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
1335 <citerefentry project='die-net'
><refentrytitle>busybox
</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
1336 <citerefentry project='die-net'
><refentrytitle>ash
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
1338 <citerefentry project='die-net'
><refentrytitle>dash
</refentrytitle><manvolnum>1</manvolnum></citerefentry>
1340 <citerefentry project='die-net'
><refentrytitle>fish
</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
1345 <term><command>set-environment
<replaceable>VARIABLE=VALUE
</replaceable>…
</command></term>
1348 <para>Set one or more systemd manager environment variables, as specified on the command
1349 line. This command will fail if variable names and values do not conform to the rules listed
1352 <xi:include href=
"version-info.xml" xpointer=
"v233"/>
1356 <term><command>unset-environment
<replaceable>VARIABLE
</replaceable>…
</command></term>
1359 <para>Unset one or more systemd manager environment
1360 variables. If only a variable name is specified, it will be
1361 removed regardless of its value. If a variable and a value
1362 are specified, the variable is only removed if it has the
1363 specified value.
</para>
1365 <xi:include href=
"version-info.xml" xpointer=
"v233"/>
1370 <command>import-environment
</command>
1371 <replaceable>VARIABLE…
</replaceable>
1375 <para>Import all, one or more environment variables set on the client into the systemd manager
1376 environment block. If a list of environment variable names is passed, client-side values are then
1377 imported into the manager's environment block. If any names are not valid environment variable
1378 names or have invalid values according to the rules described above, an error is raised. If no
1379 arguments are passed, the entire environment block inherited by the
<command>systemctl
</command>
1380 process is imported. In this mode, any inherited invalid environment variables are quietly
1383 <para>Importing of the full inherited environment block (calling this command without any
1384 arguments) is deprecated. A shell will set dozens of variables which only make sense locally and
1385 are only meant for processes which are descendants of the shell. Such variables in the global
1386 environment block are confusing to other processes.
</para>
1388 <xi:include href=
"version-info.xml" xpointer=
"v209"/>
1395 <title>Manager State Commands
</title>
1399 <term><command>daemon-reload
</command></term>
1402 <para>Reload the systemd manager configuration. This will
1403 rerun all generators (see
1404 <citerefentry><refentrytitle>systemd.generator
</refentrytitle><manvolnum>7</manvolnum></citerefentry>),
1405 reload all unit files, and recreate the entire dependency
1406 tree. While the daemon is being reloaded, all sockets
1407 systemd listens on behalf of user configuration will stay
1410 <para>This command should not be confused with the
1411 <command>reload
</command> command.
</para>
1416 <term><command>daemon-reexec
</command></term>
1419 <para>Reexecute the systemd manager. This will serialize the
1420 manager state, reexecute the process and deserialize the
1421 state again. This command is of little use except for
1422 debugging and package upgrades. Sometimes, it might be
1423 helpful as a heavy-weight
<command>daemon-reload
</command>.
1424 While the daemon is being reexecuted, all sockets systemd listening
1425 on behalf of user configuration will stay accessible.
1430 <varlistentry id='log-level'
>
1431 <term><command>log-level
</command> [
<replaceable>LEVEL
</replaceable>]
</term>
1433 <listitem><para>If no argument is given, print the current log level of the manager. If an
1434 optional argument
<replaceable>LEVEL
</replaceable> is provided, then the command changes the
1435 current log level of the manager to
<replaceable>LEVEL
</replaceable> (accepts the same values as
1436 <option>--log-level=
</option> described in
1437 <citerefentry><refentrytitle>systemd
</refentrytitle><manvolnum>1</manvolnum></citerefentry>).
1440 <xi:include href=
"version-info.xml" xpointer=
"v244"/></listitem>
1444 <term><command>log-target
</command> [
<replaceable>TARGET
</replaceable>]
</term>
1446 <listitem><para>If no argument is given, print the current log target of the manager. If an
1447 optional argument
<replaceable>TARGET
</replaceable> is provided, then the command changes the
1448 current log target of the manager to
<replaceable>TARGET
</replaceable> (accepts the same values as
1449 <option>--log-target=
</option>, described in
1450 <citerefentry><refentrytitle>systemd
</refentrytitle><manvolnum>1</manvolnum></citerefentry>).
1453 <xi:include href=
"version-info.xml" xpointer=
"v244"/></listitem>
1457 <term><command>service-watchdogs
</command> [yes|no]
</term>
1459 <listitem><para>If no argument is given, print the current state of service runtime watchdogs of
1460 the manager. If an optional boolean argument is provided, then globally enables or disables the
1461 service runtime watchdogs (
<option>WatchdogSec=
</option>) and emergency actions (e.g.
1462 <option>OnFailure=
</option> or
<option>StartLimitAction=
</option>); see
1463 <citerefentry><refentrytitle>systemd.service
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
1464 The hardware watchdog is not affected by this setting.
</para>
1466 <xi:include href=
"version-info.xml" xpointer=
"v244"/></listitem>
1472 <title>System Commands
</title>
1476 <term><command>is-system-running
</command></term>
1479 <para>Checks whether the system is operational. This
1480 returns success (exit code
0) when the system is fully up
1481 and running, specifically not in startup, shutdown or
1482 maintenance mode, and with no failed services. Failure is
1483 returned otherwise (exit code non-zero). In addition, the
1484 current state is printed in a short string to standard
1485 output, see the table below. Use
<option>--quiet
</option> to
1486 suppress this output.
</para>
1488 <para>Use
<option>--wait
</option> to wait until the boot
1489 process is completed before printing the current state and
1490 returning the appropriate error status. If
<option>--wait
</option>
1491 is in use, states
<varname>initializing
</varname> or
1492 <varname>starting
</varname> will not be reported, instead
1493 the command will block until a later state (such as
1494 <varname>running
</varname> or
<varname>degraded
</varname>)
1498 <title><command>is-system-running
</command> output
</title>
1500 <colspec colname='name'
/>
1501 <colspec colname='description'
/>
1502 <colspec colname='exit-code'
/>
1506 <entry>Description
</entry>
1507 <entry>Exit Code
</entry>
1512 <entry><varname>initializing
</varname></entry>
1513 <entry><para>Early bootup, before
1514 <filename>basic.target
</filename> is reached
1515 or the
<varname>maintenance
</varname> state entered.
1517 <entry>> 0</entry>
1520 <entry><varname>starting
</varname></entry>
1521 <entry><para>Late bootup, before the job queue
1522 becomes idle for the first time, or one of the
1523 rescue targets are reached.
</para></entry>
1524 <entry>> 0</entry>
1527 <entry><varname>running
</varname></entry>
1528 <entry><para>The system is fully
1529 operational.
</para></entry>
1533 <entry><varname>degraded
</varname></entry>
1534 <entry><para>The system is operational but one or more
1535 units failed.
</para></entry>
1536 <entry>> 0</entry>
1539 <entry><varname>maintenance
</varname></entry>
1540 <entry><para>The rescue or emergency target is
1541 active.
</para></entry>
1542 <entry>> 0</entry>
1545 <entry><varname>stopping
</varname></entry>
1546 <entry><para>The manager is shutting
1547 down.
</para></entry>
1548 <entry>> 0</entry>
1551 <entry><varname>offline
</varname></entry>
1552 <entry><para>The manager is not
1553 running. Specifically, this is the operational
1554 state if an incompatible program is running as
1555 system manager (PID
1).
</para></entry>
1556 <entry>> 0</entry>
1559 <entry><varname>unknown
</varname></entry>
1560 <entry><para>The operational state could not be
1561 determined, due to lack of resources or another
1562 error cause.
</para></entry>
1563 <entry>> 0</entry>
1569 <xi:include href=
"version-info.xml" xpointer=
"v215"/>
1574 <term><command>default
</command></term>
1577 <para>Enter default mode. This is equivalent to
<command>systemctl isolate default.target
</command>. This
1578 operation is blocking by default, use
<option>--no-block
</option> to request asynchronous behavior.
</para>
1583 <term><command>rescue
</command></term>
1586 <para>Enter rescue mode. This is equivalent to
<command>systemctl isolate rescue.target
</command>. This
1587 operation is blocking by default, use
<option>--no-block
</option> to request asynchronous behavior.
</para>
1591 <term><command>emergency
</command></term>
1594 <para>Enter emergency mode. This is equivalent to
<command>systemctl isolate
1595 emergency.target
</command>. This operation is blocking by default, use
<option>--no-block
</option> to
1596 request asynchronous behavior.
</para>
1600 <term><command>halt
</command></term>
1603 <para>Shut down and halt the system. This is mostly equivalent to
<command>systemctl start halt.target
1604 --job-mode=replace-irreversibly --no-block
</command>, but also prints a wall message to all users. This command is
1605 asynchronous; it will return after the halt operation is enqueued, without waiting for it to complete. Note
1606 that this operation will simply halt the OS kernel after shutting down, leaving the hardware powered
1607 on. Use
<command>systemctl poweroff
</command> for powering off the system (see below).
</para>
1609 <para>If combined with
<option>--force
</option>, shutdown of all running services is skipped, however all
1610 processes are killed and all file systems are unmounted or mounted read-only, immediately followed by the
1611 system halt. If
<option>--force
</option> is specified twice, the operation is immediately executed without
1612 terminating any processes or unmounting any file systems. This may result in data loss. Note that when
1613 <option>--force
</option> is specified twice the halt operation is executed by
<command>systemctl
</command>
1614 itself, and the system manager is not contacted. This means the command should succeed even when the system
1615 manager has crashed.
</para>
1617 <para>If combined with
<option>--when=
</option>, shutdown will be scheduled after the given timestamp.
1618 And
<option>--when=cancel
</option> will cancel the shutdown.
</para>
1622 <term><command>poweroff
</command></term>
1625 <para>Shut down and power-off the system. This is mostly equivalent to
<command>systemctl start
1626 poweroff.target --job-mode=replace-irreversibly --no-block
</command>, but also prints a wall message to all
1627 users. This command is asynchronous; it will return after the power-off operation is enqueued, without
1628 waiting for it to complete.
</para>
1630 <para>This command honors
<option>--force
</option> and
<option>--when=
</option> in a similar way
1631 as
<command>halt
</command>.
</para>
1635 <term><command>reboot
</command></term>
1638 <para>Shut down and reboot the system.
</para>
1640 <para>This command mostly equivalent to
<command>systemctl start reboot.target
1641 --job-mode=replace-irreversibly --no-block
</command>, but also prints a wall message to all
1642 users. This command is asynchronous; it will return after the reboot operation is enqueued,
1643 without waiting for it to complete.
</para>
1645 <para>If the switch
<option>--reboot-argument=
</option> is given, it will be passed as the optional
1646 argument to the
<citerefentry><refentrytitle>reboot
</refentrytitle><manvolnum>2</manvolnum></citerefentry>
1649 <para>Options
<option>--boot-loader-entry=
</option>,
<option>--boot-loader-menu=
</option>, and
1650 <option>--firmware-setup
</option> can be used to select what to do
<emphasis>after
</emphasis> the
1651 reboot. See the descriptions of those options for details.
</para>
1653 <para>This command honors
<option>--force
</option> and
<option>--when=
</option> in a similar way
1654 as
<command>halt
</command>.
</para>
1656 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
1661 <term><command>kexec
</command></term>
1664 <para>Shut down and reboot the system via
<command>kexec
</command>. This command will load a
1665 kexec kernel if one wasn't loaded yet or fail. A kernel may be loaded earlier by a separate step,
1666 this is particularly useful if a custom initrd or additional kernel command line options are
1667 desired. The
<option>--force
</option> can be used to continue without a kexec kernel, i.e. to
1668 perform a normal reboot. The final reboot step is equivalent to
1669 <command>systemctl start kexec.target --job-mode=replace-irreversibly --no-block
</command>.
1672 <para>To load a kernel, an enumeration is performed following the
1673 <ulink url=
"https://uapi-group.org/specifications/specs/boot_loader_specification">Boot Loader Specification
</ulink>,
1674 and the default boot entry is loaded. For this step to succeed, the system must be using UEFI
1675 and the boot loader entries must be configured appropriately.
<command>bootctl list
</command>
1676 may be used to list boot entries, see
1677 <citerefentry><refentrytitle>bootctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
1680 <para>This command is asynchronous; it will return after the reboot operation is enqueued,
1681 without waiting for it to complete.
</para>
1683 <para>This command honors
<option>--force
</option> and
<option>--when=
</option> similarly
1684 to
<command>halt
</command>.
</para>
1689 <term><command>soft-reboot
</command></term>
1692 <para>Shut down and reboot userspace. This is equivalent to
<command>systemctl start
1693 soft-reboot.target --job-mode=replace-irreversibly --no-block
</command>. This command is
1694 asynchronous; it will return after the reboot operation is enqueued, without waiting for it to
1697 <para>This command honors
<option>--force
</option> and
<option>--when=
</option> in a similar way
1698 as
<command>halt
</command>.
</para>
1700 <para>This operation only reboots userspace, leaving the kernel running. See
1701 <citerefentry><refentrytitle>systemd-soft-reboot.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>
1704 <xi:include href=
"version-info.xml" xpointer=
"v254"/>
1709 <term><command>exit
</command> <optional><replaceable>EXIT_CODE
</replaceable></optional></term>
1712 <para>Ask the service manager to quit. This is only supported for user service managers (i.e. in
1713 conjunction with the
<option>--user
</option> option) or in containers and is equivalent to
1714 <command>poweroff
</command> otherwise. This command is asynchronous; it will return after the exit
1715 operation is enqueued, without waiting for it to complete.
</para>
1717 <para>The service manager will exit with the specified exit code, if
1718 <replaceable>EXIT_CODE
</replaceable> is passed.
</para>
1720 <xi:include href=
"version-info.xml" xpointer=
"v227"/>
1725 <term><command>switch-root
</command> <optional><replaceable>ROOT
</replaceable> <optional><replaceable>INIT
</replaceable></optional></optional></term>
1728 <para>Switches to a different root directory and executes a new system manager process below it.
1729 This is intended for use in the initrd, and will transition from the initrd's system manager
1730 process (a.k.a.
"init" process, PID
1) to the main system manager process which is loaded from
1731 the actual host root files system. This call takes two arguments: the directory that is to become
1732 the new root directory, and the path to the new system manager binary below it to execute as PID
1733 1. If both are omitted or the former is an empty string it defaults to
1734 <filename>/sysroot/
</filename>. If the latter is omitted or is an empty string, a systemd binary
1735 will automatically be searched for and used as service manager. If the system manager path is
1736 omitted, equal to the empty string or identical to the path to the systemd binary, the state of
1737 the initrd's system manager process is passed to the main system manager, which allows later
1738 introspection of the state of the services involved in the initrd boot phase.
</para>
1740 <xi:include href=
"version-info.xml" xpointer=
"v209"/>
1745 <term><command>suspend
</command></term>
1748 <para>Suspend the system. This will trigger activation of the special target unit
1749 <filename>suspend.target
</filename>. This command is asynchronous, and will return after the suspend
1750 operation is successfully enqueued. It will not wait for the suspend/resume cycle to complete.
</para>
1755 <term><command>hibernate
</command></term>
1758 <para>Hibernate the system. This will trigger activation of the special target unit
1759 <filename>hibernate.target
</filename>. This command is asynchronous, and will return after the hibernation
1760 operation is successfully enqueued. It will not wait for the hibernate/thaw cycle to complete.
</para>
1765 <term><command>hybrid-sleep
</command></term>
1768 <para>Hibernate and suspend the system. This will trigger activation of the special target unit
1769 <filename>hybrid-sleep.target
</filename>. This command is asynchronous, and will return after the hybrid
1770 sleep operation is successfully enqueued. It will not wait for the sleep/wake-up cycle to complete.
</para>
1772 <xi:include href=
"version-info.xml" xpointer=
"v196"/>
1777 <term><command>suspend-then-hibernate
</command></term>
1780 <para>Suspend the system and hibernate it after the delay specified in
<filename>systemd-sleep.conf
</filename>.
1781 This will trigger activation of the special target unit
<filename>suspend-then-hibernate.target
</filename>.
1782 This command is asynchronous, and will return after the hybrid sleep operation is successfully enqueued.
1783 It will not wait for the sleep/wake-up or hibernate/thaw cycle to complete.
</para>
1785 <xi:include href=
"version-info.xml" xpointer=
"v240"/>
1792 <title>Parameter Syntax
</title>
1794 <para>Unit commands listed above take either a single unit name (designated as
<replaceable>UNIT
</replaceable>),
1795 or multiple unit specifications (designated as
<replaceable>PATTERN
</replaceable>…). In the first case, the
1796 unit name with or without a suffix must be given. If the suffix is not specified (unit name is
"abbreviated"),
1797 systemctl will append a suitable suffix,
<literal>.service
</literal> by default, and a type-specific suffix in
1798 case of commands which operate only on specific unit types. For example,
1799 <programlisting># systemctl start sshd
</programlisting> and
1800 <programlisting># systemctl start sshd.service
</programlisting>
1801 are equivalent, as are
1802 <programlisting># systemctl isolate default
</programlisting>
1804 <programlisting># systemctl isolate default.target
</programlisting>
1805 Note that (absolute) paths to device nodes are automatically converted to device unit names, and other (absolute)
1806 paths to mount unit names.
1807 <programlisting># systemctl status /dev/sda
1808 # systemctl status /home
</programlisting>
1810 <programlisting># systemctl status dev-sda.device
1811 # systemctl status home.mount
</programlisting>
1812 In the second case, shell-style globs will be matched against the primary names of all units currently in memory;
1813 literal unit names, with or without a suffix, will be treated as in the first case. This means that literal unit
1814 names always refer to exactly one unit, but globs may match zero units and this is not considered an
1817 <para>Glob patterns use
1818 <citerefentry project='man-pages'
><refentrytitle>fnmatch
</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
1819 so normal shell-style globbing rules are used, and
1820 <literal>*
</literal>,
<literal>?
</literal>,
1821 <literal>[]
</literal> may be used. See
1822 <citerefentry project='man-pages'
><refentrytitle>glob
</refentrytitle><manvolnum>7</manvolnum></citerefentry>
1823 for more details. The patterns are matched against the primary names of
1824 units currently in memory, and patterns which do not match anything
1825 are silently skipped. For example:
1826 <programlisting># systemctl stop sshd@*.service
</programlisting>
1827 will stop all
<filename>sshd@.service
</filename> instances. Note that alias names of units, and units that aren't
1828 in memory are not considered for glob expansion.
1831 <para>For unit file commands, the specified
<replaceable>UNIT
</replaceable> should be the name of the unit file
1832 (possibly abbreviated, see above), or the absolute path to the unit file:
1833 <programlisting># systemctl enable foo.service
</programlisting>
1835 <programlisting># systemctl link /path/to/foo.service
</programlisting>
1842 <title>Options
</title>
1844 <para>The following options are understood:
</para>
1848 <term><option>-t
</option></term>
1849 <term><option>--type=
</option></term>
1852 <para>The argument is a comma-separated list of unit types such as
<option>service
</option> and
1853 <option>socket
</option>. When units are listed with
<command>list-units
</command>,
1854 <command>list-dependencies
</command>,
<command>show
</command>, or
<command>status
</command>,
1855 only units of the specified types will be shown. By default, units of all types are shown.
</para>
1857 <para>As a special case, if one of the arguments is
<option>help
</option>, a list of allowed values
1858 will be printed and the program will exit.
</para>
1863 <term><option>--state=
</option></term>
1866 <para>The argument is a comma-separated list of unit LOAD, SUB, or ACTIVE states. When listing
1867 units with
<command>list-units
</command>,
<command>list-dependencies
</command>,
<command>show
</command>
1868 or
<command>status
</command>, show only those in the specified states. Use
<option>--state=failed
</option>
1869 or
<option>--failed
</option> to show only failed units.
</para>
1871 <para>As a special case, if one of the arguments is
<option>help
</option>, a list of allowed values
1872 will be printed and the program will exit.
</para>
1874 <xi:include href=
"version-info.xml" xpointer=
"v206"/>
1879 <term><option>-p
</option></term>
1880 <term><option>--property=
</option></term>
1883 <para>When showing unit/job/manager properties with the
1884 <command>show
</command> command, limit display to properties
1885 specified in the argument. The argument should be a
1886 comma-separated list of property names, such as
1887 <literal>MainPID
</literal>. Unless specified, all known
1888 properties are shown. If specified more than once, all
1889 properties with the specified names are shown. Shell
1890 completion is implemented for property names.
</para>
1892 <para>For the manager itself,
1893 <command>systemctl show
</command>
1894 will show all available properties, most of which are derived or closely match the options described in
1895 <citerefentry><refentrytitle>systemd-system.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
1898 <para>Properties for units vary by unit type, so showing any
1899 unit (even a non-existent one) is a way to list properties
1900 pertaining to this type. Similarly, showing any job will list
1901 properties pertaining to all jobs. Properties for units are
1903 <citerefentry><refentrytitle>systemd.unit
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
1904 and the pages for individual unit types
1905 <citerefentry><refentrytitle>systemd.service
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
1906 <citerefentry><refentrytitle>systemd.socket
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
1912 <term><option>-P
</option></term>
1915 <para>Equivalent to
<option>--value
</option> <option>--property=
</option>, i.e. shows the
1916 value of the property without the property name or
<literal>=
</literal>. Note that using
1917 <option>-P
</option> once will also affect all properties listed with
1918 <option>-p
</option>/
<option>--property=
</option>.
</para>
1920 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
1925 <term><option>-a
</option></term>
1926 <term><option>--all
</option></term>
1929 <para>When listing units with
<command>list-units
</command>, also show inactive units and
1930 units which are following other units. When showing unit/job/manager properties, show all
1931 properties regardless whether they are set or not.
</para>
1933 <para>To list all units installed in the file system, use the
1934 <command>list-unit-files
</command> command instead.
</para>
1936 <para>When listing units with
<command>list-dependencies
</command>, recursively show
1937 dependencies of all dependent units (by default only dependencies of target units are
1940 <para>When used with
<command>status
</command>, show journal messages in full, even if they include
1941 unprintable characters or are very long. By default, fields with unprintable characters are
1942 abbreviated as
"blob data". (Note that the pager may escape unprintable characters again.)
</para>
1947 <term><option>-r
</option></term>
1948 <term><option>--recursive
</option></term>
1951 <para>When listing units, also show units of local
1952 containers. Units of local containers will be prefixed with
1953 the container name, separated by a single colon character
1954 (
<literal>:
</literal>).
</para>
1956 <xi:include href=
"version-info.xml" xpointer=
"v212"/>
1961 <term><option>--reverse
</option></term>
1964 <para>Show reverse dependencies between units with
1965 <command>list-dependencies
</command>, i.e. follow
1966 dependencies of type
<varname>WantedBy=
</varname>,
1967 <varname>RequiredBy=
</varname>,
<varname>UpheldBy=
</varname>,
1968 <varname>PartOf=
</varname>,
<varname>BoundBy=
</varname>,
1969 instead of
<varname>Wants=
</varname> and similar.
1972 <xi:include href=
"version-info.xml" xpointer=
"v203"/>
1977 <term><option>--after
</option></term>
1980 <para>With
<command>list-dependencies
</command>, show the
1981 units that are ordered before the specified unit. In other
1982 words, recursively list units following the
1983 <varname>After=
</varname> dependency.
</para>
1985 <para>Note that any
<varname>After=
</varname> dependency is
1986 automatically mirrored to create a
1987 <varname>Before=
</varname> dependency. Temporal dependencies
1988 may be specified explicitly, but are also created implicitly
1989 for units which are
<varname>WantedBy=
</varname> targets
1991 <citerefentry><refentrytitle>systemd.target
</refentrytitle><manvolnum>5</manvolnum></citerefentry>),
1992 and as a result of other directives (for example
1993 <varname>RequiresMountsFor=
</varname>). Both explicitly
1994 and implicitly introduced dependencies are shown with
1995 <command>list-dependencies
</command>.
</para>
1997 <para>When passed to the
<command>list-jobs
</command> command, for each printed job show which other jobs are
1998 waiting for it. May be combined with
<option>--before
</option> to show both the jobs waiting for each job as
1999 well as all jobs each job is waiting for.
</para>
2001 <xi:include href=
"version-info.xml" xpointer=
"v203"/>
2006 <term><option>--before
</option></term>
2009 <para>With
<command>list-dependencies
</command>, show the
2010 units that are ordered after the specified unit. In other
2011 words, recursively list units following the
2012 <varname>Before=
</varname> dependency.
</para>
2014 <para>When passed to the
<command>list-jobs
</command> command, for each printed job show which other jobs it
2015 is waiting for. May be combined with
<option>--after
</option> to show both the jobs waiting for each job as
2016 well as all jobs each job is waiting for.
</para>
2018 <xi:include href=
"version-info.xml" xpointer=
"v212"/>
2023 <term><option>--with-dependencies
</option></term>
2026 <para>When used with
<command>status
</command>,
2027 <command>cat
</command>,
<command>list-units
</command>, and
2028 <command>list-unit-files
</command>, those commands print all
2029 specified units and the dependencies of those units.
</para>
2031 <para>Options
<option>--reverse
</option>,
2032 <option>--after
</option>,
<option>--before
</option>
2033 may be used to change what types of dependencies
2036 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
2041 <term><option>-l
</option></term>
2042 <term><option>--full
</option></term>
2045 <para>Do not ellipsize unit names, process tree entries,
2046 journal output, or truncate unit descriptions in the output
2047 of
<command>status
</command>,
<command>list-units
</command>,
2048 <command>list-jobs
</command>, and
2049 <command>list-timers
</command>.
</para>
2050 <para>Also, show installation targets in the output of
2051 <command>is-enabled
</command>.
</para>
2056 <term><option>--value
</option></term>
2059 <para>When printing properties with
<command>show
</command>, only print the value, and skip the
2060 property name and
<literal>=
</literal>. Also see option
<option>-P
</option> above.
</para>
2062 <xi:include href=
"version-info.xml" xpointer=
"v230"/>
2067 <term><option>--show-types
</option></term>
2070 <para>When showing sockets, show the type of the socket.
</para>
2072 <xi:include href=
"version-info.xml" xpointer=
"v202"/>
2077 <term><option>--job-mode=
</option></term>
2080 <para>When queuing a new job, this option controls how to deal with
2081 already queued jobs. It takes one of
<literal>fail
</literal>,
2082 <literal>replace
</literal>,
2083 <literal>replace-irreversibly
</literal>,
2084 <literal>isolate
</literal>,
2085 <literal>ignore-dependencies
</literal>,
2086 <literal>ignore-requirements
</literal>,
2087 <literal>flush
</literal>,
2088 <literal>triggering
</literal>, or
2089 <literal>restart-dependencies
</literal>. Defaults to
2090 <literal>replace
</literal>, except when the
2091 <command>isolate
</command> command is used which implies the
2092 <literal>isolate
</literal> job mode.
</para>
2094 <para>If
<literal>fail
</literal> is specified and a requested
2095 operation conflicts with a pending job (more specifically:
2096 causes an already pending start job to be reversed into a stop
2097 job or vice versa), cause the operation to fail.
</para>
2099 <para>If
<literal>replace
</literal> (the default) is
2100 specified, any conflicting pending job will be replaced, as
2103 <para>If
<literal>replace-irreversibly
</literal> is specified,
2104 operate like
<literal>replace
</literal>, but also mark the new
2105 jobs as irreversible. This prevents future conflicting
2106 transactions from replacing these jobs (or even being enqueued
2107 while the irreversible jobs are still pending). Irreversible
2108 jobs can still be cancelled using the
<command>cancel
</command>
2109 command. This job mode should be used on any transaction which
2110 pulls in
<filename>shutdown.target
</filename>.
</para>
2112 <para><literal>isolate
</literal> is only valid for start
2113 operations and causes all other units to be stopped when the
2114 specified unit is started. This mode is always used when the
2115 <command>isolate
</command> command is used.
</para>
2117 <para><literal>flush
</literal> will cause all queued jobs to
2118 be canceled when the new job is enqueued.
</para>
2120 <para>If
<literal>ignore-dependencies
</literal> is specified,
2121 then all unit dependencies are ignored for this new job and
2122 the operation is executed immediately. If passed, no required
2123 units of the unit passed will be pulled in, and no ordering
2124 dependencies will be honored. This is mostly a debugging and
2125 rescue tool for the administrator and should not be used by
2126 applications.
</para>
2128 <para><literal>ignore-requirements
</literal> is similar to
2129 <literal>ignore-dependencies
</literal>, but only causes the
2130 requirement dependencies to be ignored, the ordering
2131 dependencies will still be honored.
</para>
2133 <para><literal>triggering
</literal> may only be used with
2134 <command>systemctl stop
</command>. In this mode, the specified
2135 unit and any active units that trigger it are stopped. See the
2137 <varname>Triggers=
</varname> in
<citerefentry><refentrytitle>systemd.unit
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
2138 for more information about triggering units.
</para>
2140 <para><literal>restart-dependencies
</literal> may only be used with
2141 <command>systemctl start
</command>. In this mode, dependencies of
2142 the specified unit will receive restart propagation, as if a restart
2143 job had been enqueued for the unit.
</para>
2145 <xi:include href=
"version-info.xml" xpointer=
"v209"/>
2150 <term><option>-T
</option></term>
2151 <term><option>--show-transaction
</option></term>
2154 <para>When enqueuing a unit job (for example as effect of a
<command>systemctl start
</command>
2155 invocation or similar), show brief information about all jobs enqueued, covering both the requested
2156 job and any added because of unit dependencies. Note that the output will only include jobs
2157 immediately part of the transaction requested. It is possible that service start-up program code
2158 run as effect of the enqueued jobs might request further jobs to be pulled in. This means that
2159 completion of the listed jobs might ultimately entail more jobs than the listed ones.
</para>
2161 <xi:include href=
"version-info.xml" xpointer=
"v242"/>
2166 <term><option>--fail
</option></term>
2169 <para>Shorthand for
<option>--job-mode=
</option>fail.
</para>
2170 <para>When used with the
<command>kill
</command> command,
2171 if no units were killed, the operation results in an error.
2174 <xi:include href=
"version-info.xml" xpointer=
"v227"/>
2179 <term><option>--check-inhibitors=
</option></term>
2182 <para>When system shutdown or sleep state is requested, this option controls checking of inhibitor
2183 locks. It takes one of
<literal>auto
</literal>,
<literal>yes
</literal> or
2184 <literal>no
</literal>. Defaults to
<literal>auto
</literal>, which will behave like
2185 <literal>yes
</literal> for interactive invocations (i.e. from a TTY) and
<literal>no
</literal> for
2186 non-interactive invocations.
<literal>yes
</literal> lets the request respect inhibitor locks.
2187 <literal>no
</literal> lets the request ignore inhibitor locks.
</para>
2189 <para>Applications can establish inhibitor locks to prevent certain important operations (such as
2190 CD burning) from being interrupted by system shutdown or sleep. Any user may take these locks and
2191 privileged users may override these locks. If any locks are taken, shutdown and sleep state
2192 requests will normally fail (unless privileged). However, if
<literal>no
</literal> is specified or
2193 <literal>auto
</literal> is specified on a non-interactive requests, the operation will be
2194 attempted. If locks are present, the operation may require additional privileges.
</para>
2196 <para>Option
<option>--force
</option> provides another way to override inhibitors.
</para>
2198 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
2203 <term><option>-i
</option></term>
2206 <para>Shortcut for
<option>--check-inhibitors=no
</option>.
</para>
2208 <xi:include href=
"version-info.xml" xpointer=
"v198"/>
2213 <term><option>--dry-run
</option></term>
2216 <para>Just print what would be done. Currently supported by verbs
2217 <command>halt
</command>,
<command>poweroff
</command>,
<command>reboot
</command>,
2218 <command>kexec
</command>,
<command>suspend
</command>,
<command>hibernate
</command>,
2219 <command>hybrid-sleep
</command>,
<command>suspend-then-hibernate
</command>,
2220 <command>default
</command>,
<command>rescue
</command>,
2221 <command>emergency
</command>, and
<command>exit
</command>.
</para>
2223 <xi:include href=
"version-info.xml" xpointer=
"v236"/>
2228 <term><option>-q
</option></term>
2229 <term><option>--quiet
</option></term>
2232 <para>Suppress printing of the results of various commands
2233 and also the hints about truncated log lines. This does not
2234 suppress output of commands for which the printed output is
2235 the only result (like
<command>show
</command>). Errors are
2236 always printed.
</para>
2241 <term><option>--no-warn
</option></term>
2244 <para>Don't generate the warnings shown by default in the following cases:
2247 <para>when
<command>systemctl
</command> is invoked without procfs mounted on
2248 <filename>/proc/
</filename>,
</para>
2251 <para>when using
<command>enable
</command> or
<command>disable
</command> on units without
2252 install information (i.e. don't have or have an empty [Install] section),
</para>
2255 <para>when using
<command>disable
</command> combined with
<option>--user
</option> on units
2256 that are enabled in global scope,
</para>
2259 <para>when a
<command>stop
</command>-ped,
<command>disable
</command>-d, or
<command>mask
</command>-ed
2260 unit still has active triggering units.
</para>
2265 <xi:include href=
"version-info.xml" xpointer=
"v253"/>
2270 <term><option>--no-block
</option></term>
2273 <para>Do not synchronously wait for the requested operation
2274 to finish. If this is not specified, the job will be
2275 verified, enqueued and
<command>systemctl
</command> will
2276 wait until the unit's start-up is completed. By passing this
2277 argument, it is only verified and enqueued. This option may not be
2278 combined with
<option>--wait
</option>.
</para>
2283 <term><option>--wait
</option></term>
2286 <para>Synchronously wait for started units to terminate again.
2287 This option may not be combined with
<option>--no-block
</option>.
2288 Note that this will wait forever if any given unit never terminates
2289 (by itself or by getting stopped explicitly); particularly services
2290 which use
<literal>RemainAfterExit=yes
</literal>.
</para>
2292 <para>When used with
<command>is-system-running
</command>, wait
2293 until the boot process is completed before returning.
</para>
2295 <xi:include href=
"version-info.xml" xpointer=
"v232"/>
2299 <xi:include href=
"user-system-options.xml" xpointer=
"user" />
2300 <xi:include href=
"user-system-options.xml" xpointer=
"system" />
2303 <term><option>--failed
</option></term>
2306 <para>List units in failed state. This is equivalent to
2307 <option>--state=failed
</option>.
</para>
2309 <xi:include href=
"version-info.xml" xpointer=
"v233"/>
2314 <term><option>--no-wall
</option></term>
2317 <para>Do not send wall message before halt, power-off and reboot.
</para>
2322 <term><option>--global
</option></term>
2325 <para>When used with
<command>enable
</command> and
2326 <command>disable
</command>, operate on the global user
2327 configuration directory, thus enabling or disabling a unit
2328 file globally for all future logins of all users.
</para>
2333 <term><option>--no-reload
</option></term>
2336 <para>When used with
<command>enable
</command> and
2337 <command>disable
</command>, do not implicitly reload daemon
2338 configuration after executing the changes.
</para>
2343 <term><option>--no-ask-password
</option></term>
2346 <para>When used with
<command>start
</command> and related
2347 commands, disables asking for passwords. Background services
2348 may require input of a password or passphrase string, for
2349 example to unlock system hard disks or cryptographic
2350 certificates. Unless this option is specified and the
2351 command is invoked from a terminal,
2352 <command>systemctl
</command> will query the user on the
2353 terminal for the necessary secrets. Use this option to
2354 switch this behavior off. In this case, the password must be
2355 supplied by some other means (for example graphical password
2356 agents) or the service might fail. This also disables
2357 querying the user for authentication for privileged
2363 <term><option>--kill-whom=
</option></term>
2366 <para>When used with
<command>kill
</command>, choose which processes to send a UNIX process signal
2367 to. Must be one of
<option>main
</option>,
<option>control
</option> or
<option>all
</option> to
2368 select whether to kill only the main process, the control process or all processes of the unit. The
2369 main process of the unit is the one that defines the life-time of it. A control process of a unit
2370 is one that is invoked by the manager to induce state changes of it. For example, all processes
2371 started due to the
<varname>ExecStartPre=
</varname>,
<varname>ExecStop=
</varname> or
2372 <varname>ExecReload=
</varname> settings of service units are control processes. Note that there is
2373 only one control process per unit at a time, as only one state change is executed at a time. For
2374 services of type
<varname>Type=forking
</varname>, the initial process started by the manager for
2375 <varname>ExecStart=
</varname> is a control process, while the process ultimately forked off by that
2376 one is then considered the main process of the unit (if it can be determined). This is different
2377 for service units of other types, where the process forked off by the manager for
2378 <varname>ExecStart=
</varname> is always the main process itself. A service unit consists of zero or
2379 one main process, zero or one control process plus any number of additional processes. Not all unit
2380 types manage processes of these types however. For example, for mount units, control processes are
2381 defined (which are the invocations of
<filename>&MOUNT_PATH;</filename> and
2382 <filename>&UMOUNT_PATH;</filename>), but no main process is defined. If omitted, defaults to
2383 <option>all
</option>.
</para>
2385 <xi:include href=
"version-info.xml" xpointer=
"v252"/>
2390 <term><option>--kill-value=
</option><replaceable>INT
</replaceable></term>
2392 <listitem><para>If used with the
<command>kill
</command> command, enqueues a signal along with the
2393 specified integer value parameter to the specified process(es). This operation is only available for
2394 POSIX Realtime Signals (i.e.
<option>--signal=SIGRTMIN+…
</option> or
2395 <option>--signal=SIGRTMAX-…
</option>), and ensures the signals are generated via the
<citerefentry
2396 project='man-pages'
><refentrytitle>sigqueue
</refentrytitle><manvolnum>3</manvolnum></citerefentry>
2397 system call, rather than
<citerefentry
2398 project='man-pages'
><refentrytitle>kill
</refentrytitle><manvolnum>3</manvolnum></citerefentry>. The
2399 specified value must be a
32-bit signed integer, and may be specified either in decimal, in
2400 hexadecimal (if prefixed with
<literal>0x
</literal>), octal (if prefixed with
<literal>0o
</literal>)
2401 or binary (if prefixed with
<literal>0b
</literal>)
</para>
2403 <para>If this option is used the signal will only be enqueued on the control or main process of the
2404 unit, never on other processes belonging to the unit, i.e.
<option>--kill-whom=all
</option> will only
2405 affect main and control processes but no other processes.
</para>
2407 <xi:include href=
"version-info.xml" xpointer=
"v254"/></listitem>
2410 <xi:include href=
"standard-options.xml" xpointer=
"signal" />
2413 <term><option>--what=
</option></term>
2416 <para>Select what type of per-unit resources to remove when the
<command>clean
</command> command is
2417 invoked, see above. Takes one of
<constant>configuration
</constant>,
<constant>state
</constant>,
2418 <constant>cache
</constant>,
<constant>logs
</constant>,
<constant>runtime
</constant>,
2419 <constant>fdstore
</constant> to select the type of resource. This option may be specified more than
2420 once, in which case all specified resource types are removed. Also accepts the special value
2421 <constant>all
</constant> as a shortcut for specifying all six resource types. If this option is not
2422 specified defaults to the combination of
<constant>cache
</constant>,
<constant>runtime
</constant>
2423 and
<constant>fdstore
</constant>, i.e. the three kinds of resources that are generally considered
2424 to be redundant and can be reconstructed on next invocation. Note that the explicit removal of the
2425 <constant>fdstore
</constant> resource type is only useful if the
2426 <varname>FileDescriptorStorePreserve=
</varname> option is enabled, since the file descriptor store
2427 is otherwise cleaned automatically when the unit is stopped.
</para>
2429 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
2434 <term><option>-f
</option></term>
2435 <term><option>--force
</option></term>
2438 <para>When used with
<command>enable
</command>, overwrite
2439 any existing conflicting symlinks.
</para>
2441 <para>When used with
<command>edit
</command>, create all of the
2442 specified units which do not already exist.
</para>
2444 <para>When used with
<command>halt
</command>,
<command>poweroff
</command>,
<command>reboot
</command> or
2445 <command>kexec
</command>, execute the selected operation without shutting down all units. However, all
2446 processes will be killed forcibly and all file systems are unmounted or remounted read-only. This is hence a
2447 drastic but relatively safe option to request an immediate reboot. If
<option>--force
</option> is specified
2448 twice for these operations (with the exception of
<command>kexec
</command>), they will be executed
2449 immediately, without terminating any processes or unmounting any file systems. Warning: specifying
2450 <option>--force
</option> twice with any of these operations might result in data loss. Note that when
2451 <option>--force
</option> is specified twice the selected operation is executed by
2452 <command>systemctl
</command> itself, and the system manager is not contacted. This means the command should
2453 succeed even when the system manager has crashed.
</para>
2458 <term><option>--message=
</option></term>
2461 <para>When used with
<command>halt
</command>,
<command>poweroff
</command> or
<command>reboot
</command>, set a
2462 short message explaining the reason for the operation. The message will be logged together with the default
2463 shutdown message.
</para>
2465 <xi:include href=
"version-info.xml" xpointer=
"v225"/>
2470 <term><option>--now
</option></term>
2473 <para>When used with
<command>enable
</command>, the units
2474 will also be started. When used with
<command>disable
</command> or
2475 <command>mask
</command>, the units will also be stopped. The start
2476 or stop operation is only carried out when the respective enable or
2477 disable operation has been successful.
</para>
2479 <xi:include href=
"version-info.xml" xpointer=
"v220"/>
2484 <term><option>--root=
</option></term>
2487 <para>When used with
2488 <command>enable
</command>/
<command>disable
</command>/
<command>is-enabled
</command>
2489 (and related commands), use the specified root path when looking for unit
2490 files. If this option is present,
<command>systemctl
</command> will operate on
2491 the file system directly, instead of communicating with the
<command>systemd
</command>
2492 daemon to carry out changes.
</para>
2498 <term><option>--image=
<replaceable>image
</replaceable></option></term>
2500 <listitem><para>Takes a path to a disk image file or block device node. If specified, all operations
2501 are applied to file system in the indicated disk image. This option is similar to
2502 <option>--root=
</option>, but operates on file systems stored in disk images or block devices. The
2503 disk image should either contain just a file system or a set of file systems within a GPT partition
2504 table, following the
<ulink url=
"https://uapi-group.org/specifications/specs/discoverable_partitions_specification">Discoverable Partitions
2505 Specification
</ulink>. For further information on supported disk images, see
2506 <citerefentry><refentrytitle>systemd-nspawn
</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s
2507 switch of the same name.
</para>
2509 <xi:include href=
"version-info.xml" xpointer=
"v252"/></listitem>
2512 <xi:include href=
"standard-options.xml" xpointer=
"image-policy-open" />
2515 <term><option>--runtime
</option></term>
2518 <para>When used with
<command>enable
</command>,
2519 <command>disable
</command>,
<command>edit
</command>,
2520 (and related commands), make changes only temporarily, so
2521 that they are lost on the next reboot. This will have the
2522 effect that changes are not made in subdirectories of
2523 <filename>/etc/
</filename> but in
<filename>/run/
</filename>,
2524 with identical immediate effects, however, since the latter
2525 is lost on reboot, the changes are lost too.
</para>
2527 <para>Similarly, when used with
2528 <command>set-property
</command>, make changes only
2529 temporarily, so that they are lost on the next
2535 <term><option>--preset-mode=
</option></term>
2538 <para>Takes one of
<literal>full
</literal> (the default),
2539 <literal>enable-only
</literal>,
2540 <literal>disable-only
</literal>. When used with the
2541 <command>preset
</command> or
<command>preset-all
</command>
2542 commands, controls whether units shall be disabled and
2543 enabled according to the preset rules, or only enabled, or
2544 only disabled.
</para>
2546 <xi:include href=
"version-info.xml" xpointer=
"v215"/>
2551 <term><option>-n
</option></term>
2552 <term><option>--lines=
</option></term>
2555 <para>When used with
<command>status
</command>, controls the number of journal lines to show,
2556 counting from the most recent ones. Takes a positive integer argument, or
0 to disable journal
2557 output. Defaults to
10.
</para>
2562 <term><option>-o
</option></term>
2563 <term><option>--output=
</option></term>
2566 <para>When used with
<command>status
</command>, controls the
2567 formatting of the journal entries that are shown. For the
2568 available choices, see
2569 <citerefentry><refentrytitle>journalctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
2570 Defaults to
<literal>short
</literal>.
</para>
2575 <term><option>--firmware-setup
</option></term>
2578 <para>When used with the
<command>reboot
</command> command, indicate to the system's firmware to
2579 reboot into the firmware setup interface. Note that this functionality is not available on all
2582 <xi:include href=
"version-info.xml" xpointer=
"v220"/>
2587 <term><option>--boot-loader-menu=
<replaceable>timeout
</replaceable></option></term>
2590 <para>When used with the
<command>reboot
</command> command, indicate to the system's boot loader to
2591 show the boot loader menu on the following boot. Takes a time value as parameter — indicating the
2592 menu timeout. Pass zero in order to disable the menu timeout. Note that not all boot loaders
2593 support this functionality.
</para>
2595 <xi:include href=
"version-info.xml" xpointer=
"v242"/>
2600 <term><option>--boot-loader-entry=
<replaceable>ID
</replaceable></option></term>
2603 <para>When used with the
<command>reboot
</command> command, indicate to the system's boot loader to
2604 boot into a specific boot loader entry on the following boot. Takes a boot loader entry identifier
2605 as argument, or
<literal>help
</literal> in order to list available entries. Note that not all boot
2606 loaders support this functionality.
</para>
2608 <xi:include href=
"version-info.xml" xpointer=
"v242"/>
2613 <term><option>--reboot-argument=
</option></term>
2616 <para>This switch is used with
<command>reboot
</command>. The value is architecture and firmware specific. As an example,
<literal>recovery
</literal>
2617 might be used to trigger system recovery, and
<literal>fota
</literal> might be used to trigger a
2618 <quote>firmware over the air
</quote> update.
</para>
2620 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
2625 <term><option>--plain
</option></term>
2628 <para>When used with
<command>list-dependencies
</command>,
2629 <command>list-units
</command> or
<command>list-machines
</command>,
2630 the output is printed as a list instead of a tree, and the bullet
2631 circles are omitted.
</para>
2633 <xi:include href=
"version-info.xml" xpointer=
"v203"/>
2638 <term><option>--timestamp=
</option></term>
2641 <para>Change the format of printed timestamps. The following values may be used:
2646 <term><option>pretty
</option> (this is the default)
</term>
2647 <listitem><para><literal>Day YYYY-MM-DD HH:MM:SS TZ
</literal></para>
2649 <xi:include href=
"version-info.xml" xpointer=
"v248"/></listitem>
2655 <term><option>unix
</option></term>
2656 <listitem><para><literal>@seconds-since-the-epoch
</literal></para>
2658 <xi:include href=
"version-info.xml" xpointer=
"v251"/></listitem>
2664 <term><option>us
</option></term>
2665 <term><option>μs
</option></term>
2666 <listitem><para><literal>Day YYYY-MM-DD HH:MM:SS.UUUUUU TZ
</literal></para>
2668 <xi:include href=
"version-info.xml" xpointer=
"v248"/></listitem>
2674 <term><option>utc
</option></term>
2675 <listitem><para><literal>Day YYYY-MM-DD HH:MM:SS UTC
</literal></para>
2677 <xi:include href=
"version-info.xml" xpointer=
"v248"/></listitem>
2683 <term><option>us+utc
</option></term>
2684 <term><option>μs+utc
</option></term>
2685 <listitem><para><literal>Day YYYY-MM-DD HH:MM:SS.UUUUUU UTC
</literal></para>
2687 <xi:include href=
"version-info.xml" xpointer=
"v248"/></listitem>
2691 <xi:include href=
"version-info.xml" xpointer=
"v247"/>
2696 <term><option>--mkdir
</option></term>
2698 <listitem><para>When used with
<command>bind
</command>, creates the destination file or directory before
2699 applying the bind mount. Note that even though the name of this option suggests that it is suitable only for
2700 directories, this option also creates the destination file node to mount over if the object to mount is not
2701 a directory, but a regular file, device node, socket or FIFO.
</para>
2703 <xi:include href=
"version-info.xml" xpointer=
"v248"/></listitem>
2707 <term><option>--marked
</option></term>
2709 <listitem><para>Only allowed with
<command>reload-or-restart
</command>. Enqueues restart jobs for all
2710 units that have the
<literal>needs-restart
</literal> mark, and reload jobs for units that have the
2711 <literal>needs-reload
</literal> mark. When a unit marked for reload does not support reload, restart
2712 will be queued. Those properties can be set using
<command>set-property Markers=…
</command>.
</para>
2714 <para>Unless
<option>--no-block
</option> is used,
<command>systemctl
</command> will wait for the
2715 queued jobs to finish.
</para>
2717 <xi:include href=
"version-info.xml" xpointer=
"v248"/></listitem>
2721 <term><option>--read-only
</option></term>
2723 <listitem><para>When used with
<command>bind
</command>, creates a read-only bind mount.
</para>
2725 <xi:include href=
"version-info.xml" xpointer=
"v248"/></listitem>
2729 <term><option>--drop-in=
</option></term>
2732 <para>When used with
<command>edit
</command>, use the given drop-in file name instead of
2733 <filename>override.conf
</filename>.
</para>
2735 <xi:include href=
"version-info.xml" xpointer=
"v253"/>
2740 <term><option>--when=
</option></term>
2743 <para>When used with
<command>halt
</command>,
<command>poweroff
</command>,
<command>reboot
</command>
2744 or
<command>kexec
</command>, schedule the action to be performed at the given timestamp,
2745 which should adhere to the syntax documented in
<citerefentry
2746 project='man-pages'
><refentrytitle>systemd.time
</refentrytitle><manvolnum>7</manvolnum></citerefentry>
2747 section
"PARSING TIMESTAMPS". Specially, if
<literal>show
</literal> is given, the currently scheduled
2748 action will be shown, which can be canceled by passing an empty string or
<literal>cancel
</literal>.
</para>
2750 <xi:include href=
"version-info.xml" xpointer=
"v254"/>
2754 <xi:include href=
"user-system-options.xml" xpointer=
"host" />
2755 <xi:include href=
"user-system-options.xml" xpointer=
"machine" />
2757 <xi:include href=
"standard-options.xml" xpointer=
"no-pager" />
2758 <xi:include href=
"standard-options.xml" xpointer=
"legend" />
2759 <xi:include href=
"standard-options.xml" xpointer=
"help" />
2760 <xi:include href=
"standard-options.xml" xpointer=
"version" />
2765 <title>Exit status
</title>
2767 <para>On success,
0 is returned, a non-zero failure code otherwise.
</para>
2769 <para><command>systemctl
</command> uses the return codes defined by LSB, as defined in
2770 <ulink url=
"http://refspecs.linuxbase.org/LSB_3.0.0/LSB-PDA/LSB-PDA/iniscrptact.html">LSB
3.0.0</ulink>.
2774 <title>LSB return codes
</title>
2779 <entry>Value
</entry>
2780 <entry>Description in LSB
</entry>
2781 <entry>Use in systemd
</entry>
2786 <entry><constant>0</constant></entry>
2787 <entry>"program is running or service is OK"</entry>
2788 <entry>unit is active
</entry>
2791 <entry><constant>1</constant></entry>
2792 <entry>"program is dead and <filename>/var/run</filename> pid file exists"</entry>
2793 <entry>unit
<emphasis>not
</emphasis> failed (used by
<command>is-failed
</command>)
</entry>
2796 <entry><constant>2</constant></entry>
2797 <entry>"program is dead and <filename>/var/lock</filename> lock file exists"</entry>
2798 <entry>unused
</entry>
2801 <entry><constant>3</constant></entry>
2802 <entry>"program is not running"</entry>
2803 <entry>unit is not active
</entry>
2806 <entry><constant>4</constant></entry>
2807 <entry>"program or service status is unknown"</entry>
2808 <entry>no such unit
</entry>
2814 <para>The mapping of LSB service states to systemd unit states is imperfect, so it is better to
2815 not rely on those return values but to look for specific unit states and substates instead.
2820 <title>Environment
</title>
2822 <variablelist class='environment-variables'
>
2824 <term><varname>$SYSTEMD_EDITOR
</varname></term>
2826 <listitem><para>Editor to use when editing units; overrides
2827 <varname>$EDITOR
</varname> and
<varname>$VISUAL
</varname>. If neither
2828 <varname>$SYSTEMD_EDITOR
</varname> nor
<varname>$EDITOR
</varname> nor
2829 <varname>$VISUAL
</varname> are present or if it is set to an empty
2830 string or if their execution failed, systemctl will try to execute well
2831 known editors in this order:
2832 <citerefentry project='die-net'
><refentrytitle>editor
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
2833 <citerefentry project='die-net'
><refentrytitle>nano
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
2834 <citerefentry project='die-net'
><refentrytitle>vim
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
2835 <citerefentry project='die-net'
><refentrytitle>vi
</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
2838 <xi:include href=
"version-info.xml" xpointer=
"v218"/></listitem>
2840 <xi:include href=
"common-variables.xml" xpointer=
"log-level"/>
2841 <xi:include href=
"common-variables.xml" xpointer=
"log-color"/>
2842 <xi:include href=
"common-variables.xml" xpointer=
"log-time"/>
2843 <xi:include href=
"common-variables.xml" xpointer=
"log-location"/>
2844 <xi:include href=
"common-variables.xml" xpointer=
"log-target"/>
2845 <xi:include href=
"common-variables.xml" xpointer=
"pager"/>
2846 <xi:include href=
"common-variables.xml" xpointer=
"less"/>
2847 <xi:include href=
"common-variables.xml" xpointer=
"lesscharset"/>
2848 <xi:include href=
"common-variables.xml" xpointer=
"lesssecure"/>
2849 <xi:include href=
"common-variables.xml" xpointer=
"colors"/>
2850 <xi:include href=
"common-variables.xml" xpointer=
"urlify"/>
2855 <title>See Also
</title>
2857 <citerefentry><refentrytitle>systemd
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
2858 <citerefentry><refentrytitle>journalctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
2859 <citerefentry><refentrytitle>loginctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
2860 <citerefentry><refentrytitle>machinectl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
2861 <citerefentry><refentrytitle>systemd.unit
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
2862 <citerefentry><refentrytitle>systemd.resource-control
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
2863 <citerefentry><refentrytitle>systemd.special
</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
2864 <citerefentry project='man-pages'
><refentrytitle>wall
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
2865 <citerefentry><refentrytitle>systemd.preset
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
2866 <citerefentry><refentrytitle>systemd.generator
</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
2867 <citerefentry project='man-pages'
><refentrytitle>glob
</refentrytitle><manvolnum>7</manvolnum></citerefentry>