1 <?xml version='1.0'?> <!--*-nxml-*-->
2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
6 This file is part of systemd.
8 Copyright 2010 Lennart Poettering
10 systemd is free software; you can redistribute it and/or modify it
11 under the terms of the GNU General Public License as published by
12 the Free Software Foundation; either version 2 of the License, or
13 (at your option) any later version.
15 systemd is distributed in the hope that it will be useful, but
16 WITHOUT ANY WARRANTY; without even the implied warranty of
17 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
18 General Public License for more details.
20 You should have received a copy of the GNU General Public License
21 along with systemd; If not, see <http://www.gnu.org/licenses/>.
24 <refentry id="systemctl">
27 <title>systemctl</title>
28 <productname>systemd</productname>
32 <contrib>Developer</contrib>
33 <firstname>Lennart</firstname>
34 <surname>Poettering</surname>
35 <email>lennart@poettering.net</email>
41 <refentrytitle>systemctl</refentrytitle>
42 <manvolnum>1</manvolnum>
46 <refname>systemctl</refname>
47 <refname>systemd-systemctl</refname>
48 <refpurpose>Control the systemd system and service manager</refpurpose>
53 <command>systemctl <arg choice="opt" rep="repeat">OPTIONS</arg> <arg choice="req">COMMAND</arg> <arg choice="opt" rep="repeat">NAME</arg></command>
58 <title>Description</title>
60 <para><command>systemctl</command> may be used to
61 introspect and control the state of the
62 <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>
63 system and service manager.</para>
67 <title>Options</title>
69 <para>The following options are understood:</para>
73 <term><option>--help</option></term>
74 <term><option>-h</option></term>
76 <listitem><para>Prints a short help
77 text and exits.</para></listitem>
81 <term><option>--version</option></term>
83 <listitem><para>Prints a short version
84 string and exits.</para></listitem>
88 <term><option>--type=</option></term>
89 <term><option>-t</option></term>
91 <listitem><para>When listing units,
92 limit display to certain unit
93 types. If not specified units of all
94 types will be shown. The argument
95 should be a unit type name such as
96 <option>service</option>,
97 <option>socket</option> and
98 similar.</para></listitem>
102 <term><option>--property=</option></term>
103 <term><option>-p</option></term>
105 <listitem><para>When showing
106 unit/job/manager properties, limit
107 display to certain properties as
108 specified as argument. If not
109 specified all set properties are
110 shown. The argument should be a
111 property name, such as
112 <literal>MainPID</literal>. If
113 specified more than once all
114 properties with the specified names
115 are shown.</para></listitem>
119 <term><option>--all</option></term>
120 <term><option>-a</option></term>
122 <listitem><para>When listing units,
123 show all units, regardless of their
124 state, including inactive units. When
125 showing unit/job/manager properties,
126 show all properties regardless whether
127 they are set or not.</para></listitem>
131 <term><option>--failed</option></term>
133 <listitem><para>When listing units,
134 show only failed units. Do not confuse
136 <option>--fail</option>.</para></listitem>
140 <term><option>--full</option></term>
142 <listitem><para>Do not ellipsize unit
143 names and truncate unit descriptions
145 <command>list-units</command> and
146 <command>list-jobs</command>.</para></listitem>
150 <term><option>--fail</option></term>
152 <listitem><para>If the requested
153 operation conflicts with a pending
154 unfinished job, fail the command. If
155 this is not specified the requested
156 operation will replace the pending job,
157 if necessary. Do not confuse
159 <option>--failed</option>.</para></listitem>
163 <term><option>--ignore-dependencies</option></term>
165 <listitem><para>When enqueuing a new
166 job ignore all its dependencies and
167 execute it immediately. If passed no
168 required units of the unit passed will
169 be pulled in, and no ordering
170 dependencies will be honoured. This is
171 mostly a debugging and rescue tool for
172 the administrator and should not be
174 applications.</para></listitem>
178 <term><option>--quiet</option></term>
179 <term><option>-q</option></term>
181 <listitem><para>Suppress output to
183 <command>snapshot</command>,
184 <command>is-active</command>,
185 <command>enable</command> and
186 <command>disable</command>.</para></listitem>
190 <term><option>--no-block</option></term>
192 <listitem><para>Do not synchronously wait for
193 the requested operation to finish. If this is
194 not specified the job will be verified,
195 enqueued and <command>systemctl</command> will
196 wait until it is completed. By passing this
197 argument it is only verified and
198 enqueued.</para></listitem>
202 <term><option>--no-legend</option></term>
204 <listitem><para>Do not print a legend, i.e.
205 the column headers and the footer with hints.
210 <term><option>--no-pager</option></term>
212 <listitem><para>Do not pipe output into a
213 pager.</para></listitem>
217 <term><option>--system</option></term>
219 <listitem><para>Talk to the systemd
220 system manager. (Default)</para></listitem>
224 <term><option>--user</option></term>
226 <listitem><para>Talk to the systemd
227 manager of the calling user.</para></listitem>
231 <term><option>--order</option></term>
232 <term><option>--require</option></term>
234 <listitem><para>When used in
236 <command>dot</command> command (see
237 below), selects which dependencies are
238 shown in the dependency graph. If
239 <option>--order</option> is passed
240 only dependencies of type
241 <varname>After=</varname> or
242 <varname>Before=</varname> are
243 shown. If <option>--require</option>
244 is passed only dependencies of type
245 <varname>Requires=</varname>,
246 <varname>RequiresOverridable=</varname>,
247 <varname>Requisite=</varname>,
248 <varname>RequisiteOverridable=</varname>,
249 <varname>Wants=</varname> and
250 <varname>Conflicts=</varname> are
251 shown. If neither is passed, shows
252 dependencies of all these
253 types.</para></listitem>
257 <term><option>--no-wall</option></term>
259 <listitem><para>Don't send wall
261 halt, power-off, reboot.</para></listitem>
265 <term><option>--global</option></term>
267 <listitem><para>When used with
268 <command>enable</command> and
269 <command>disable</command>, operate on the
270 global user configuration
271 directory, thus enabling or disabling
272 a unit file globally for all future
273 logins of all users.</para></listitem>
277 <term><option>--no-reload</option></term>
279 <listitem><para>When used with
280 <command>enable</command> and
281 <command>disable</command>, do not
282 implicitly reload daemon configuration
284 changes.</para></listitem>
288 <term><option>--no-ask-password</option></term>
290 <listitem><para>When used with
291 <command>start</command> and related
292 commands, disables asking for
293 passwords. Background services may
294 require input of a password or
295 passphrase string, for example to
296 unlock system hard disks or
297 cryptographic certificates. Unless
298 this option is specified and the
299 command is invoked from a terminal
300 <command>systemctl</command> will
301 query the user on the terminal for the
302 necessary secrets. Use this option to
303 switch this behavior off. In this
304 case the password must be supplied by
305 some other means (for example
306 graphical password agents) or the
307 service might fail.</para></listitem>
311 <term><option>--kill-who=</option></term>
313 <listitem><para>When used with
314 <command>kill</command>, choose which
315 processes to kill. Must be one of
316 <option>main</option>,
317 <option>control</option> or
318 <option>all</option> to select whether
319 to kill only the main process of the
320 unit, the control process or all
321 processes of the unit. If omitted
323 <option>all</option>.</para></listitem>
327 <term><option>--signal=</option></term>
328 <term><option>-s</option></term>
330 <listitem><para>When used with
331 <command>kill</command>, choose which
332 signal to send to selected
333 processes. Must be one of the well
334 known signal specifiers such as
335 SIGTERM, SIGINT or SIGSTOP. If
337 <option>SIGTERM</option>.</para></listitem>
341 <term><option>--force</option></term>
342 <term><option>-f</option></term>
344 <listitem><para>When used with
345 <command>enable</command>, override any
347 symlinks.</para></listitem>
349 <listitem><para>When used with
350 <command>halt</command>,
351 <command>poweroff</command>,
352 <command>reboot</command> or
353 <command>kexec</command> execute the
354 selected operation without shutting
355 down all units. However, all processes
356 will be killed forcibly and all file
357 systems are unmounted or remounted
358 read-only. This is hence a drastic but
359 relatively safe option to request an
361 <option>--force</option> is specified
362 twice for these operations, they will
363 be executed immediately without
364 terminating any processes or umounting
365 any file systems. Warning: specifying
366 <option>--force</option> twice with
367 any of these operations might result
368 in data loss.</para></listitem>
372 <term><option>--root=</option></term>
374 <listitem><para>When used with
375 <command>enable</command>/<command>disable</command>/<command>is-enabled</command> (and
376 related commands), use alternative
377 root path when looking for unit
378 files.</para></listitem>
382 <term><option>--runtime</option></term>
384 <listitem><para>When used with
385 <command>enable</command>/<command>disable</command>/<command>is-enabled</command> (and related commands), make
386 changes only temporarily, so that they
387 are dropped on the next reboot. This
388 will have the effect that changes are
389 not made in subdirectories of
390 <filename>/etc</filename> but in
391 <filename>/run</filename>, with
392 identical immediate effects, however,
393 since the latter is lost on reboot,
395 too.</para></listitem>
399 <term><option>-H</option></term>
400 <term><option>--host</option></term>
402 <listitem><para>Execute operation
403 remotely. Specify a hostname, or
404 username and hostname separated by @,
405 to connect to. This will use SSH to
406 talk to the remote systemd
407 instance.</para></listitem>
411 <term><option>-P</option></term>
412 <term><option>--privileged</option></term>
414 <listitem><para>Acquire privileges via
415 PolicyKit before executing the
416 operation.</para></listitem>
420 <term><option>--lines=</option></term>
421 <term><option>-n</option></term>
423 <listitem><para>When used with
424 <command>status</command> controls the
425 number of journal lines to show,
426 counting from the most recent
427 ones. Takes a positive integer
428 argument. Defaults to
429 10.</para></listitem>
433 <term><option>--follow</option></term>
434 <term><option>-f</option></term>
436 <listitem><para>When used with
437 <command>status</command> continously
438 prints new journal entries as they are
440 journal.</para></listitem>
444 <term><option>--output=</option></term>
445 <term><option>-o</option></term>
447 <listitem><para>When used with
448 <command>status</command> controls the
449 formatting of the journal entries that
450 are shown. For the available choices
452 <citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>. Defaults
454 <literal>short</literal>.</para></listitem>
459 <para>The following commands are understood:</para>
463 <term><command>list-units</command></term>
465 <listitem><para>List known units.</para></listitem>
468 <term><command>start [NAME...]</command></term>
470 <listitem><para>Start (activate) one
471 or more units specified on the command
472 line.</para></listitem>
475 <term><command>stop [NAME...]</command></term>
477 <listitem><para>Stop (deactivate) one
478 or more units specified on the command
479 line.</para></listitem>
482 <term><command>reload [NAME...]</command></term>
484 <listitem><para>Asks all units listed
485 on the command line to reload their
486 configuration. Note that this will
487 reload the service-specific
488 configuration, not the unit
489 configuration file of systemd. If you
490 want systemd to reload the
491 configuration file of a unit use the
492 <command>daemon-reload</command>
493 command. In other words: for the
494 example case of Apache, this will
496 <filename>httpd.conf</filename> in the
498 <filename>apache.service</filename>
499 systemd unit file. </para>
501 <para>This command should not be
503 <command>daemon-reload</command> or
504 <command>load</command>
505 commands.</para></listitem>
509 <term><command>restart [NAME...]</command></term>
511 <listitem><para>Restart one or more
512 units specified on the command
513 line. If the units are not running yet
515 started.</para></listitem>
518 <term><command>try-restart [NAME...]</command></term>
520 <listitem><para>Restart one or more
521 units specified on the command
522 line if the units are running. Do
523 nothing if units are not running.
524 Note that for compatibility
525 with Red Hat init scripts
526 <command>condrestart</command> is
527 equivalent to this command.</para></listitem>
530 <term><command>reload-or-restart [NAME...]</command></term>
532 <listitem><para>Reload one or more
533 units if they support it. If not,
534 restart them instead. If the units
535 are not running yet they will be
536 started.</para></listitem>
539 <term><command>reload-or-try-restart [NAME...]</command></term>
541 <listitem><para>Reload one or more
542 units if they support it. If not,
543 restart them instead. Do nothing if
544 the units are not running. Note that
545 for compatibility with SysV init
547 <command>force-reload</command> is
549 command.</para></listitem>
552 <term><command>isolate [NAME]</command></term>
554 <listitem><para>Start the unit
555 specified on the command line and its
556 dependencies and stop all others.</para>
558 <para>This is similar to changing the
559 runlevel in a traditional init system. The
560 <command>isolate</command> command will
561 immediately stop processes that are not
562 enabled in the new unit, possibly including
563 the graphical environment or terminal you
564 are currently using.</para>
566 <para>Note that this works only on units
567 where <option>AllowIsolate=</option> is
569 <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
570 for details.</para></listitem>
573 <term><command>kill [NAME...]</command></term>
575 <listitem><para>Send a signal to one
576 or more processes of the unit. Use
577 <option>--kill-who=</option> to select
578 which process to kill. Use
579 <option>--kill-mode=</option> to
580 select the kill mode and
581 <option>--signal=</option> to select
582 the signal to send.</para></listitem>
585 <term><command>is-active [NAME...]</command></term>
587 <listitem><para>Check whether any of
588 the specified units are active
589 (i.e. running). Returns an exit code
590 0 if at least one is active, non-zero
592 <option>--quiet</option> is specified
593 this will also print the current unit
594 state to STDOUT.</para></listitem>
597 <term><command>status [NAME...|PID...]</command></term>
599 <listitem><para>Show terse runtime
600 status information about one or more
601 units, followed by its most recent log
602 data from the journal. This function
603 is intended to generate human-readable
604 output. If you are looking for
605 computer-parsable output, use
606 <command>show</command> instead. If a
607 PID is passed information about the
608 unit the process of the PID belongs to
609 is shown.</para></listitem>
612 <term><command>show [NAME...|JOB...]</command></term>
614 <listitem><para>Show properties of one
615 or more units, jobs or the manager
616 itself. If no argument is specified
617 properties of the manager will be
618 shown. If a unit name is specified
619 properties of the unit is shown, and
620 if a job id is specified properties of
621 the job is shown. By default, empty
622 properties are suppressed. Use
623 <option>--all</option> to show those
624 too. To select specific properties to
626 <option>--property=</option>. This
627 command is intended to be used
628 whenever computer-parsable output is
630 <command>status</command> if you are
631 looking for formatted human-readable
632 output.</para></listitem>
636 <term><command>reset-failed [NAME...]</command></term>
638 <listitem><para>Reset the
639 '<literal>failed</literal>' state of the
640 specified units, or if no unit name is
641 passed of all units. When a unit fails
642 in some way (i.e. process exiting with
643 non-zero error code, terminating
644 abnormally or timing out) it will
645 automatically enter the
646 '<literal>failed</literal>' state and
647 its exit code and status is recorded
648 for introspection by the administrator
649 until the service is restarted or
651 command.</para></listitem>
655 <term><command>list-unit-files</command></term>
657 <listitem><para>List installed unit files.
662 <term><command>enable [NAME...]</command></term>
664 <listitem><para>Enable one or more
665 unit files, as specified on the
666 command line. This will create a
667 number of symlinks as encoded in the
668 <literal>[Install]</literal> sections
669 of the unit files. After the symlinks
670 have been created the systemd
671 configuration is reloaded (in a way
672 that is equivalent to
673 <command>daemon-reload</command>) to
674 ensure the changes are taken into
675 account immediately. Note that this
676 does not have the effect that any of
677 the units enabled are also started at
678 the same time. If this is desired a
679 separate <command>start</command>
680 command must be invoked for the
683 <para>This command will
684 print the actions executed. This
685 output may be suppressed by passing
686 <option>--quiet</option>.</para>
688 <para>Note that this operation creates
689 only the suggested symlinks for the
690 units. While this command is the
691 recommended way to manipulate the unit
692 configuration directory, the
693 administrator is free to make
694 additional changes manually, by
695 placing or removing symlinks in the
696 directory. This is particularly useful
697 to create configurations that deviate
698 from the suggested default
699 installation. In this case the
700 administrator must make sure to invoke
701 <command>daemon-reload</command>
702 manually as necessary, to ensure his
703 changes are taken into account.</para>
705 <para>Enabling units should not be
706 confused with starting (activating)
707 units, as done by the
708 <command>start</command>
709 command. Enabling and starting units
710 is orthogonal: units may be enabled
711 without being started and started
712 without being enabled. Enabling simply
713 hooks the unit into various suggested
714 places (for example, so that the unit
715 is automatically started on boot or
716 when a particular kind of hardware is
717 plugged in). Starting actually spawns
718 the daemon process (in case of service
719 units), or binds the socket (in case
720 of socket units), and so
723 <para>Depending on whether
724 <option>--system</option>,
725 <option>--user</option> or
726 <option>--global</option> is specified
727 this enables the unit for the system,
728 for the calling user only
729 or for all future logins of all
730 users. Note that in the latter case no
731 systemd daemon configuration is
737 <term><command>disable [NAME...]</command></term>
739 <listitem><para>Disables one or more
740 units. This removes all symlinks to
741 the specified unit files from the unit
742 configuration directory, and hence
743 undoes the changes made by
744 <command>enable</command>. Note
745 however that this removes
746 all symlinks to the unit files
747 (i.e. including manual additions), not
748 just those actually created by
749 <command>enable</command>. This call
750 implicitly reloads the systemd daemon
751 configuration after completing the
752 disabling of the units. Note that this
753 command does not implicitly stop the
754 units that is being disabled. If this
755 is desired an additional
756 <command>stop</command>command should
757 be executed afterwards.</para>
759 <para>This command will print the
760 actions executed. This output may be
761 suppressed by passing
762 <option>--quiet</option>.</para>
765 <para>This command honors
766 <option>--system</option>,
767 <option>--user</option>,
768 <option>--global</option> in a similar
770 <command>enable</command>.</para>
774 <term><command>is-enabled [NAME...]</command></term>
776 <listitem><para>Checks whether any of
777 the specified unit files is enabled
779 <command>enable</command>). Returns an
780 exit code of 0 if at least one is
781 enabled, non-zero otherwise. Prints
782 the current enable status. To suppress
784 <option>--quiet</option>.</para></listitem>
788 <term><command>reenable [NAME...]</command></term>
790 <listitem><para>Reenable one or more
791 unit files, as specified on the
792 command line. This is a combination of
793 <command>disable</command> and
794 <command>enable</command> and is
795 useful to reset the symlinks a unit is
796 enabled with to the defaults
798 <literal>[Install]</literal> section
799 of the unit file.</para>
804 <term><command>preset [NAME...]</command></term>
806 <listitem><para>Reset one or more unit
807 files, as specified on the command
808 line, to the defaults configured in a
809 preset file. This has the same effect
810 as <command>disable</command> or
811 <command>enable</command>, depending
812 how the unit is listed in the preset
818 <term><command>mask [NAME...]</command></term>
820 <listitem><para>Mask one or more unit
821 files, as specified on the command
822 line. This will link these units to
823 <filename>/dev/null</filename>, making
824 it impossible to start them. This is a stronger version
825 of <command>disable</command>, since
826 it prohibits all kinds of activation
827 of the unit, including manual
828 activation. Use this option with
834 <term><command>unmask [NAME...]</command></term>
836 <listitem><para>Unmask one or more
837 unit files, as specified on the
838 command line. This will undo the
840 <command>mask</command>.</para>
845 <term><command>link [NAME...]</command></term>
847 <listitem><para>Link a unit file that
848 is not in the unit file search paths
849 into the unit file search path. This
850 requires an absolute path to a unit
851 file. The effect of this can be undone
852 with <command>disable</command>. The
853 effect of this command is that a unit
854 file is available for
855 <command>start</command> and other
856 commands although it isn't installed
857 directly in the unit search
863 <term><command>load [NAME...]</command></term>
865 <listitem><para>Load one or more units
866 specified on the command line. This
867 will simply load their configuration
868 from disk, but not start them. To
869 start them you need to use the
870 <command>start</command> command which
871 will implicitly load a unit that has
872 not been loaded yet. Note that systemd
873 garbage collects loaded units that are
874 not active or referenced by an active
875 unit. This means that units loaded
876 this way will usually not stay loaded
877 for long. Also note that this command
878 cannot be used to reload unit
879 configuration. Use the
880 <command>daemon-reload</command>
881 command for that. All in all, this
882 command is of little use except for
884 <para>This command should not be
886 <command>daemon-reload</command> or
887 <command>reload</command>
888 commands.</para></listitem>
891 <term><command>list-jobs</command></term>
893 <listitem><para>List jobs that are in progress.</para></listitem>
896 <term><command>cancel [JOB...]</command></term>
898 <listitem><para>Cancel one or more
899 jobs specified on the command line by
901 IDs. If no job id is specified, cancel all pending jobs.</para></listitem>
904 <term><command>dump</command></term>
906 <listitem><para>Dump server
907 status. This will output a (usually
908 very long) human readable manager
909 status dump. Its format is subject to
910 change without notice and should not
912 applications.</para></listitem>
915 <term><command>dot</command></term>
917 <listitem><para>Generate textual
918 dependency graph description in dot
919 format for further processing with the
921 <citerefentry><refentrytitle>dot</refentrytitle><manvolnum>1</manvolnum></citerefentry>
922 tool. Use a command line like
923 <command>systemctl dot | dot -Tsvg >
924 systemd.svg</command> to generate a
925 graphical dependency tree. Unless
926 <option>--order</option> or
927 <option>--require</option> is passed
928 the generated graph will show both
929 ordering and requirement
930 dependencies.</para></listitem>
933 <term><command>snapshot [NAME]</command></term>
935 <listitem><para>Create a snapshot. If
936 a snapshot name is specified, the new
937 snapshot will be named after it. If
938 none is specified an automatic
939 snapshot name is generated. In either
940 case, the snapshot name used is
941 printed to STDOUT, unless
942 <option>--quiet</option> is
945 <para>A snapshot refers to a saved
946 state of the systemd manager. It is
947 implemented itself as a unit that is
948 generated dynamically with this
949 command and has dependencies on all
950 units active at the time. At a later
951 time the user may return to this state
953 <command>isolate</command> command on
954 the snapshot unit.</para></listitem>
956 <para>Snapshots are only useful for
957 saving and restoring which units are
958 running or are stopped, they do not
959 save/restore any other
960 state. Snapshots are dynamic and lost
964 <term><command>delete [NAME...]</command></term>
966 <listitem><para>Remove a snapshot
967 previously created with
968 <command>snapshot</command>.</para></listitem>
971 <term><command>daemon-reload</command></term>
973 <listitem><para>Reload systemd manager
974 configuration. This will reload all
975 unit files and recreate the entire
976 dependency tree. While the daemon is
977 reloaded, all sockets systemd listens
978 on on behalf of user configuration will
979 stay accessible.</para> <para>This
980 command should not be confused with
981 the <command>load</command> or
982 <command>reload</command>
983 commands.</para></listitem>
986 <term><command>daemon-reexec</command></term>
988 <listitem><para>Reexecute the systemd
989 manager. This will serialize the
990 manager state, reexecute the process
991 and deserialize the state again. This
992 command is of little use except for
993 debugging and package
994 upgrades. Sometimes it might be
995 helpful as a heavy-weight
996 <command>daemon-reload</command>. While
997 the daemon is reexecuted all sockets
998 systemd listens on on behalf of user
999 configuration will stay
1000 accessible.</para></listitem>
1003 <term><command>show-environment</command></term>
1005 <listitem><para>Dump the systemd
1006 manager environment block. The
1007 environment block will be dumped in
1008 straight-forward form suitable for
1009 sourcing into a shell script. This
1010 environment block will be passed to
1011 all processes the manager
1012 spawns.</para></listitem>
1015 <term><command>set-environment [NAME=VALUE...]</command></term>
1017 <listitem><para>Set one or more
1018 systemd manager environment variables,
1019 as specified on the command
1020 line.</para></listitem>
1023 <term><command>unset-environment [NAME...]</command></term>
1025 <listitem><para>Unset one or more
1026 systemd manager environment
1027 variables. If only a variable name is
1028 specified it will be removed
1029 regardless of its value. If a variable
1030 and a value are specified the variable
1031 is only removed if it has the
1032 specified value.</para></listitem>
1035 <term><command>default</command></term>
1037 <listitem><para>Enter default
1038 mode. This is mostly equivalent to
1040 default.target</command>.</para></listitem>
1043 <term><command>rescue</command></term>
1045 <listitem><para>Enter rescue
1046 mode. This is mostly equivalent to
1048 rescue.target</command> but also
1049 prints a wall message to all
1050 users.</para></listitem>
1053 <term><command>emergency</command></term>
1055 <listitem><para>Enter emergency
1056 mode. This is mostly equivalent to
1058 emergency.target</command> but also
1059 prints a wall message to all
1060 users.</para></listitem>
1063 <term><command>halt</command></term>
1065 <listitem><para>Shut down and halt the
1066 system. This is mostly equivalent to
1067 <command>start halt.target</command>
1068 but also prints a wall message to all
1069 users. If combined with
1070 <option>--force</option> shutdown of
1071 all running services is skipped,
1072 however all processes are killed and
1073 all file systems are unmounted or
1074 mounted read-only, immediately
1075 followed by the system halt. If
1076 <option>--force</option> is specified
1077 twice the the operation is immediately
1078 executed without terminating any
1079 processes or unmounting any file
1080 systems. This may result in data
1081 loss.</para></listitem>
1084 <term><command>poweroff</command></term>
1086 <listitem><para>Shut down and
1087 power-off the system. This is mostly
1088 equivalent to <command>start
1089 poweroff.target</command> but also
1090 prints a wall message to all users. If
1091 combined with <option>--force</option>
1092 shutdown of all running services is
1093 skipped, however all processes are
1094 killed and all file systems are
1095 unmounted or mounted read-only,
1096 immediately followed by the powering
1097 off. If <option>--force</option> is
1098 specified twice the the operation is
1099 immediately executed without
1100 terminating any processes or
1101 unmounting any file systems. This may
1102 result in data loss.</para></listitem>
1105 <term><command>reboot</command></term>
1107 <listitem><para>Shut down and reboot
1108 the system. This is mostly equivalent
1110 reboot.target</command> but also
1111 prints a wall message to all users. If
1112 combined with <option>--force</option>
1113 shutdown of all running services is
1114 skipped, however all processes are
1115 killed and all file systems are
1116 unmounted or mounted read-only,
1117 immediately followed by the reboot. If
1118 <option>--force</option> is specified
1119 twice the the operation is immediately
1120 executed without terminating any
1121 processes or unmounting any file
1122 systems. This may result in data
1123 loss.</para></listitem>
1126 <term><command>kexec</command></term>
1128 <listitem><para>Shut down and reboot
1129 the system via kexec. This is mostly
1130 equivalent to <command>start
1131 kexec.target</command> but also prints
1132 a wall message to all users. If
1133 combined with <option>--force</option>
1134 shutdown of all running services is
1135 skipped, however all processes are killed
1136 and all file systems are unmounted or
1137 mounted read-only, immediately
1139 reboot.</para></listitem>
1142 <term><command>exit</command></term>
1144 <listitem><para>Ask the systemd
1145 manager to quit. This is only
1146 supported for user service managers
1147 (i.e. in conjunction with the
1148 <option>--user</option> option) and
1149 will fail otherwise.</para></listitem>
1156 <title>Exit status</title>
1158 <para>On success 0 is returned, a non-zero failure
1159 code otherwise.</para>
1163 <title>Environment</title>
1167 <term><varname>$SYSTEMD_PAGER</varname></term>
1168 <listitem><para>Pager to use when
1169 <option>--no-pager</option> is not given;
1170 overrides <varname>$PAGER</varname>. Setting
1171 this to an empty string or the value
1172 <literal>cat</literal> is equivalent to passing
1173 <option>--no-pager</option>.</para></listitem>
1179 <title>See Also</title>
1181 <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
1182 <citerefentry><refentrytitle>systemadm</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
1183 <citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
1184 <citerefentry><refentrytitle>loginctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
1185 <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
1186 <citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
1187 <citerefentry><refentrytitle>wall</refentrytitle><manvolnum>1</manvolnum></citerefentry>