]>
Commit | Line | Data |
---|---|---|
514094f9 | 1 | <?xml version='1.0'?> |
3a54a157 ZJS |
2 | <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" |
3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ | |
681eb9cf FB |
4 | <!ENTITY % entities SYSTEM "custom-entities.ent" > |
5 | %entities; | |
6 | ]> | |
0307f791 | 7 | <!-- SPDX-License-Identifier: LGPL-2.1+ --> |
7874bcd6 | 8 | |
21ac6ff1 ZJS |
9 | <refentry id="systemctl" |
10 | xmlns:xi="http://www.w3.org/2001/XInclude"> | |
7874bcd6 | 11 | |
4a6022f0 ZJS |
12 | <refentryinfo> |
13 | <title>systemctl</title> | |
14 | <productname>systemd</productname> | |
4a6022f0 ZJS |
15 | </refentryinfo> |
16 | ||
17 | <refmeta> | |
18 | <refentrytitle>systemctl</refentrytitle> | |
19 | <manvolnum>1</manvolnum> | |
20 | </refmeta> | |
21 | ||
22 | <refnamediv> | |
23 | <refname>systemctl</refname> | |
24 | <refpurpose>Control the systemd system and service manager</refpurpose> | |
25 | </refnamediv> | |
26 | ||
27 | <refsynopsisdiv> | |
28 | <cmdsynopsis> | |
29 | <command>systemctl</command> | |
30 | <arg choice="opt" rep="repeat">OPTIONS</arg> | |
31 | <arg choice="plain">COMMAND</arg> | |
da5e955f | 32 | <arg choice="opt" rep="repeat">UNIT</arg> |
4a6022f0 ZJS |
33 | </cmdsynopsis> |
34 | </refsynopsisdiv> | |
35 | ||
36 | <refsect1> | |
37 | <title>Description</title> | |
38 | ||
a4390b6b LP |
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 | |
4a6022f0 | 42 | <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry> |
a4390b6b LP |
43 | for an introduction into the basic concepts and functionality this |
44 | tool manages.</para> | |
4a6022f0 ZJS |
45 | </refsect1> |
46 | ||
47 | <refsect1> | |
e1fac8a6 | 48 | <title>Commands</title> |
4a6022f0 | 49 | |
e1fac8a6 | 50 | <para>The following commands are understood:</para> |
4a6022f0 | 51 | |
e1fac8a6 ZJS |
52 | <refsect2> |
53 | <title>Unit Commands</title> | |
20b3f379 | 54 | |
e1fac8a6 ZJS |
55 | <variablelist> |
56 | <varlistentry> | |
57 | <term><command>list-units</command> <optional><replaceable>PATTERN</replaceable>…</optional></term> | |
4a6022f0 | 58 | |
e1fac8a6 ZJS |
59 | <listitem> |
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> | |
4a6022f0 | 67 | |
e1fac8a6 ZJS |
68 | <para>Produces output similar to |
69 | <programlisting> UNIT LOAD ACTIVE SUB DESCRIPTION | |
70 | sys-module-fuse.device loaded active plugged /sys/module/fuse | |
71 | -.mount loaded active mounted Root Mount | |
72 | boot-efi.mount loaded active mounted /boot/efi | |
73 | systemd-journald.service loaded active running Journal Service | |
74 | systemd-logind.service loaded active running Login Service | |
75 | ● user@1000.service loaded failed failed User Manager for UID 1000 | |
76 | … | |
77 | systemd-tmpfiles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories | |
9b9b3d36 | 78 | |
e1fac8a6 ZJS |
79 | LOAD = Reflects whether the unit definition was properly loaded. |
80 | ACTIVE = The high-level unit activation state, i.e. generalization of SUB. | |
81 | SUB = The low-level unit activation state, values depend on unit type. | |
e16972e6 | 82 | |
e1fac8a6 ZJS |
83 | 123 loaded units listed. Pass --all to see loaded but inactive units, too. |
84 | To show all installed unit files use 'systemctl list-unit-files'. | |
85 | </programlisting> | |
86 | The header and the last unit of a given type are underlined if the | |
87 | terminal supports that. A colored dot is shown next to services which | |
88 | were masked, not found, or otherwise failed.</para> | |
9b9b3d36 | 89 | |
e1fac8a6 ZJS |
90 | <para>The LOAD column shows the load state, one of <constant>loaded</constant>, |
91 | <constant>not-found</constant>, <constant>bad-setting</constant>, <constant>error</constant>, | |
92 | <constant>masked</constant>. The ACTIVE columns shows the general unit state, one of | |
93 | <constant>active</constant>, <constant>reloading</constant>, <constant>inactive</constant>, | |
94 | <constant>failed</constant>, <constant>activating</constant>, <constant>deactivating</constant>. The SUB | |
95 | column shows the unit-type-specific detailed state of the unit, possible values vary by unit type. The list | |
96 | of possible LOAD, ACTIVE, and SUB states is not constant and new systemd releases may both add and remove | |
97 | values. <programlisting>systemctl --state=help</programlisting> command maybe be used to display the | |
98 | current set of possible values.</para> | |
4a6022f0 | 99 | |
e1fac8a6 ZJS |
100 | <para>This is the default command.</para> |
101 | </listitem> | |
102 | </varlistentry> | |
ea539eb6 | 103 | |
e1fac8a6 ZJS |
104 | <varlistentry> |
105 | <term><command>list-sockets</command> <optional><replaceable>PATTERN</replaceable>…</optional></term> | |
ea539eb6 | 106 | |
e1fac8a6 ZJS |
107 | <listitem> |
108 | <para>List socket units currently in memory, ordered by listening address. If one or more | |
109 | <replaceable>PATTERN</replaceable>s are specified, only socket units matching one of them are | |
110 | shown. Produces output similar to | |
111 | <programlisting> | |
112 | LISTEN UNIT ACTIVATES | |
113 | /dev/initctl systemd-initctl.socket systemd-initctl.service | |
114 | … | |
115 | [::]:22 sshd.socket sshd.service | |
116 | kobject-uevent 1 systemd-udevd-kernel.socket systemd-udevd.service | |
4a6022f0 | 117 | |
e1fac8a6 ZJS |
118 | 5 sockets listed.</programlisting> |
119 | Note: because the addresses might contains spaces, this output | |
120 | is not suitable for programmatic consumption. | |
121 | </para> | |
4a6022f0 | 122 | |
e1fac8a6 ZJS |
123 | <para>Also see <option>--show-types</option>, <option>--all</option>, and <option>--state=</option>.</para> |
124 | </listitem> | |
125 | </varlistentry> | |
21b587cf | 126 | |
e1fac8a6 ZJS |
127 | <varlistentry> |
128 | <term><command>list-timers</command> <optional><replaceable>PATTERN</replaceable>…</optional></term> | |
e9fbae3f | 129 | |
e1fac8a6 ZJS |
130 | <listitem> |
131 | <para>List timer units currently in memory, ordered by the time they elapse next. If one or more | |
132 | <replaceable>PATTERN</replaceable>s are specified, only units matching one of them are shown. | |
133 | Produces output similar to | |
134 | <programlisting> | |
135 | NEXT LEFT LAST PASSED UNIT ACTIVATES | |
136 | n/a n/a Thu 2017-02-23 13:40:29 EST 3 days ago ureadahead-stop.timer ureadahead-stop.service | |
137 | 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 | |
138 | 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 | |
139 | 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 | |
140 | </programlisting> | |
141 | </para> | |
4fa226ff | 142 | |
e1fac8a6 ZJS |
143 | <para><emphasis>NEXT</emphasis> shows the next time the timer will run.</para> |
144 | <para><emphasis>LEFT</emphasis> shows how long till the next time the timer runs.</para> | |
145 | <para><emphasis>LAST</emphasis> shows the last time the timer ran.</para> | |
146 | <para><emphasis>PASSED</emphasis> shows how long has passed since the timer last ran.</para> | |
147 | <para><emphasis>UNIT</emphasis> shows the name of the timer</para> | |
148 | <para><emphasis>ACTIVATES</emphasis> shows the name the service the timer activates when it runs.</para> | |
4a6022f0 | 149 | |
e1fac8a6 ZJS |
150 | <para>Also see <option>--all</option> and <option>--state=</option>.</para> |
151 | </listitem> | |
152 | </varlistentry> | |
1238ee09 | 153 | |
e1fac8a6 ZJS |
154 | <varlistentry> |
155 | <term><command>start <replaceable>PATTERN</replaceable>…</command></term> | |
1238ee09 | 156 | |
e1fac8a6 | 157 | <listitem> |
1d56bc09 ZJS |
158 | <para>Start (activate) one or more units specified on the command line.</para> |
159 | ||
160 | <para>Note that unit glob patterns expand to names of units currently in memory. Units which are | |
161 | not active and are not in a failed state usually are not in memory, and will not be matched by | |
162 | any pattern. In addition, in case of instantiated units, systemd is often unaware of the instance | |
163 | name until the instance has been started. Therefore, using glob patterns with | |
164 | <command>start</command> has limited usefulness. Also, secondary alias names of units are not | |
165 | considered.</para> | |
166 | ||
167 | <para>Option <option>--all</option> may be used to also operate on inactive units which are | |
168 | referenced by other loaded units. Note that this is not the same as operating on "all" possible | |
169 | units, because as the previous paragraph describes, such a list is ill-defined. Nevertheless, | |
170 | <command>systemctl start --all <replaceable>GLOB</replaceable></command> may be useful if all the | |
171 | units that should match the pattern are pulled in by some target which is known to be loaded. | |
172 | </para> | |
e1fac8a6 ZJS |
173 | </listitem> |
174 | </varlistentry> | |
175 | <varlistentry> | |
176 | <term><command>stop <replaceable>PATTERN</replaceable>…</command></term> | |
afba4199 | 177 | |
e1fac8a6 ZJS |
178 | <listitem> |
179 | <para>Stop (deactivate) one or more units specified on the command line.</para> | |
9029f642 | 180 | |
e1fac8a6 ZJS |
181 | <para>This command will fail if the unit does not exist or if stopping of the unit is prohibited (see |
182 | <varname>RefuseManualStop=</varname> in | |
183 | <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>). | |
184 | It will <emphasis>not</emphasis> fail if any of the commands configured to stop the unit | |
185 | (<varname>ExecStop=</varname>, etc.) fail, because the manager will still forcibly terminate the | |
186 | unit.</para> | |
187 | </listitem> | |
188 | </varlistentry> | |
189 | <varlistentry> | |
190 | <term><command>reload <replaceable>PATTERN</replaceable>…</command></term> | |
f6375e83 | 191 | |
e1fac8a6 ZJS |
192 | <listitem> |
193 | <para>Asks all units listed on the command line to reload | |
194 | their configuration. Note that this will reload the | |
195 | service-specific configuration, not the unit configuration | |
196 | file of systemd. If you want systemd to reload the | |
197 | configuration file of a unit, use the | |
198 | <command>daemon-reload</command> command. In other words: | |
199 | for the example case of Apache, this will reload Apache's | |
200 | <filename>httpd.conf</filename> in the web server, not the | |
201 | <filename>apache.service</filename> systemd unit | |
202 | file.</para> | |
82948f6c | 203 | |
e1fac8a6 ZJS |
204 | <para>This command should not be confused with the |
205 | <command>daemon-reload</command> command.</para> | |
206 | </listitem> | |
9029f642 | 207 | |
e1fac8a6 ZJS |
208 | </varlistentry> |
209 | <varlistentry> | |
210 | <term><command>restart <replaceable>PATTERN</replaceable>…</command></term> | |
afba4199 | 211 | |
e1fac8a6 ZJS |
212 | <listitem> |
213 | <para>Stop and then start one or more units specified on the command line. If the units are not running | |
214 | yet, they will be started.</para> | |
afba4199 | 215 | |
e1fac8a6 ZJS |
216 | <para>Note that restarting a unit with this command does not necessarily flush out all of the unit's |
217 | resources before it is started again. For example, the per-service file descriptor storage facility (see | |
218 | <varname>FileDescriptorStoreMax=</varname> in | |
219 | <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>) will | |
220 | remain intact as long as the unit has a job pending, and is only cleared when the unit is fully stopped and | |
221 | no jobs are pending anymore. If it is intended that the file descriptor store is flushed out, too, during a | |
222 | restart operation an explicit <command>systemctl stop</command> command followed by <command>systemctl | |
223 | start</command> should be issued.</para> | |
224 | </listitem> | |
225 | </varlistentry> | |
226 | <varlistentry> | |
227 | <term><command>try-restart <replaceable>PATTERN</replaceable>…</command></term> | |
4a6022f0 | 228 | |
e1fac8a6 ZJS |
229 | <listitem> |
230 | <para>Stop and then start one or more units specified on the | |
231 | command line if the units are running. This does nothing | |
232 | if units are not running.</para> | |
233 | <!-- Note that we don't document condrestart here, as that is just compatibility support, and we generally | |
234 | don't document that. --> | |
235 | </listitem> | |
236 | </varlistentry> | |
237 | <varlistentry> | |
238 | <term><command>reload-or-restart <replaceable>PATTERN</replaceable>…</command></term> | |
4a6022f0 | 239 | |
e1fac8a6 ZJS |
240 | <listitem> |
241 | <para>Reload one or more units if they support it. If not, stop and then start them instead. If the units | |
242 | are not running yet, they will be started.</para> | |
243 | </listitem> | |
244 | </varlistentry> | |
245 | <varlistentry> | |
246 | <term><command>try-reload-or-restart <replaceable>PATTERN</replaceable>…</command></term> | |
4f9a9105 | 247 | |
e1fac8a6 ZJS |
248 | <listitem> |
249 | <para>Reload one or more units if they support it. If not, stop and then start them instead. This does | |
250 | nothing if the units are not running.</para> | |
251 | <!-- Note that we don't document force-reload here, as that is just compatibility support, and we generally | |
252 | don't document that. --> | |
253 | </listitem> | |
254 | </varlistentry> | |
255 | <varlistentry> | |
256 | <term><command>isolate <replaceable>UNIT</replaceable></command></term> | |
4f9a9105 | 257 | |
e1fac8a6 ZJS |
258 | <listitem> |
259 | <para>Start the unit specified on the command line and its dependencies | |
260 | and stop all others, unless they have | |
261 | <option>IgnoreOnIsolate=yes</option> (see | |
262 | <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>). | |
263 | If a unit name with no extension is given, an extension of | |
264 | <literal>.target</literal> will be assumed.</para> | |
991f2a39 | 265 | |
e1fac8a6 ZJS |
266 | <para>This is similar to changing the runlevel in a |
267 | traditional init system. The <command>isolate</command> | |
268 | command will immediately stop processes that are not enabled | |
269 | in the new unit, possibly including the graphical | |
270 | environment or terminal you are currently using.</para> | |
991f2a39 | 271 | |
e1fac8a6 ZJS |
272 | <para>Note that this is allowed only on units where |
273 | <option>AllowIsolate=</option> is enabled. See | |
274 | <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> | |
275 | for details.</para> | |
276 | </listitem> | |
277 | </varlistentry> | |
278 | <varlistentry> | |
279 | <term><command>kill <replaceable>PATTERN</replaceable>…</command></term> | |
23ade460 | 280 | |
e1fac8a6 ZJS |
281 | <listitem> |
282 | <para>Send a signal to one or more processes of the | |
283 | unit. Use <option>--kill-who=</option> to select which | |
284 | process to kill. Use <option>--signal=</option> to select | |
285 | the signal to send.</para> | |
286 | </listitem> | |
287 | </varlistentry> | |
288 | <varlistentry> | |
289 | <term><command>clean <replaceable>PATTERN</replaceable>…</command></term> | |
4dc5b821 | 290 | |
e1fac8a6 ZJS |
291 | <listitem> |
292 | <para>Remove the configuration, state, cache, logs or runtime data of the specified units. Use | |
293 | <option>--what=</option> to select which kind of resource to remove. For service units this may | |
294 | be used to remove the directories configured with <varname>ConfigurationDirectory=</varname>, | |
295 | <varname>StateDirectory=</varname>, <varname>CacheDirectory=</varname>, | |
296 | <varname>LogsDirectory=</varname> and <varname>RuntimeDirectory=</varname>, see | |
297 | <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry> | |
298 | for details. For timer units this may be used to clear out the persistent timestamp data if | |
299 | <varname>Persistent=</varname> is used and <option>--what=state</option> is selected, see | |
300 | <citerefentry><refentrytitle>systemd.timer</refentrytitle><manvolnum>5</manvolnum></citerefentry>. This | |
301 | command only applies to units that use either of these settings. If <option>--what=</option> is | |
302 | not specified, both the cache and runtime data are removed (as these two types of data are | |
303 | generally redundant and reproducible on the next invocation of the unit).</para> | |
304 | </listitem> | |
305 | </varlistentry> | |
306 | <varlistentry> | |
307 | <term><command>is-active <replaceable>PATTERN</replaceable>…</command></term> | |
4dc5b821 | 308 | |
e1fac8a6 ZJS |
309 | <listitem> |
310 | <para>Check whether any of the specified units are active | |
311 | (i.e. running). Returns an exit code | |
312 | <constant>0</constant> if at least one is active, or | |
313 | non-zero otherwise. Unless <option>--quiet</option> is | |
314 | specified, this will also print the current unit state to | |
315 | standard output.</para> | |
316 | </listitem> | |
317 | </varlistentry> | |
318 | <varlistentry> | |
319 | <term><command>is-failed <replaceable>PATTERN</replaceable>…</command></term> | |
4dc5b821 | 320 | |
e1fac8a6 ZJS |
321 | <listitem> |
322 | <para>Check whether any of the specified units are in a | |
323 | "failed" state. Returns an exit code | |
324 | <constant>0</constant> if at least one has failed, | |
325 | non-zero otherwise. Unless <option>--quiet</option> is | |
326 | specified, this will also print the current unit state to | |
327 | standard output.</para> | |
328 | </listitem> | |
329 | </varlistentry> | |
330 | <varlistentry> | |
331 | <term><command>status</command> <optional><replaceable>PATTERN</replaceable>…|<replaceable>PID</replaceable>…]</optional></term> | |
4dc5b821 | 332 | |
e1fac8a6 ZJS |
333 | <listitem> |
334 | <para>Show terse runtime status information about one or | |
335 | more units, followed by most recent log data from the | |
336 | journal. If no units are specified, show system status. If | |
337 | combined with <option>--all</option>, also show the status of | |
338 | all units (subject to limitations specified with | |
339 | <option>-t</option>). If a PID is passed, show information | |
340 | about the unit the process belongs to.</para> | |
4dc5b821 | 341 | |
e1fac8a6 ZJS |
342 | <para>This function is intended to generate human-readable |
343 | output. If you are looking for computer-parsable output, | |
344 | use <command>show</command> instead. By default, this | |
345 | function only shows 10 lines of output and ellipsizes | |
346 | lines to fit in the terminal window. This can be changed | |
347 | with <option>--lines</option> and <option>--full</option>, | |
348 | see above. In addition, <command>journalctl | |
349 | --unit=<replaceable>NAME</replaceable></command> or | |
350 | <command>journalctl | |
351 | --user-unit=<replaceable>NAME</replaceable></command> use | |
352 | a similar filter for messages and might be more | |
353 | convenient. | |
354 | </para> | |
4dc5b821 | 355 | |
e1fac8a6 ZJS |
356 | <para>systemd implicitly loads units as necessary, so just running the <command>status</command> will |
357 | attempt to load a file. The command is thus not useful for determining if something was already loaded or | |
358 | not. The units may possibly also be quickly unloaded after the operation is completed if there's no reason | |
359 | to keep it in memory thereafter. | |
360 | </para> | |
4dc5b821 | 361 | |
e1fac8a6 ZJS |
362 | <example> |
363 | <title>Example output from systemctl status </title> | |
4a6022f0 | 364 | |
e1fac8a6 ZJS |
365 | <programlisting>$ systemctl status bluetooth |
366 | ● bluetooth.service - Bluetooth service | |
367 | Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) | |
368 | Active: active (running) since Wed 2017-01-04 13:54:04 EST; 1 weeks 0 days ago | |
369 | Docs: man:bluetoothd(8) | |
370 | Main PID: 930 (bluetoothd) | |
371 | Status: "Running" | |
372 | Tasks: 1 | |
373 | Memory: 648.0K | |
374 | CPU: 435ms | |
375 | CGroup: /system.slice/bluetooth.service | |
376 | └─930 /usr/lib/bluetooth/bluetoothd | |
4a6022f0 | 377 | |
e1fac8a6 ZJS |
378 | Jan 12 10:46:45 example.com bluetoothd[8900]: Not enough free handles to register service |
379 | Jan 12 10:46:45 example.com bluetoothd[8900]: Current Time Service could not be registered | |
380 | Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output error (5) | |
381 | </programlisting> | |
df4a7cb7 | 382 | |
e1fac8a6 ZJS |
383 | <para>The dot ("●") uses color on supported terminals to summarize the unit state at a glance. White |
384 | indicates an <literal>inactive</literal> or <literal>deactivating</literal> state. Red indicates a | |
385 | <literal>failed</literal> or <literal>error</literal> state and green indicates an | |
386 | <literal>active</literal>, <literal>reloading</literal> or <literal>activating</literal> state. | |
387 | </para> | |
df4a7cb7 | 388 | |
e1fac8a6 ZJS |
389 | <para>The "Loaded:" line in the output will show <literal>loaded</literal> if the unit has been loaded into |
390 | memory. Other possible values for "Loaded:" include: <literal>error</literal> if there was a problem | |
391 | loading it, <literal>not-found</literal> if not unit file was found for this unit, | |
392 | <literal>bad-setting</literal> if an essential unit file setting could not be parsed and | |
393 | <literal>masked</literal> if the unit file has been masked. Along with showing the path to the unit file, | |
394 | this line will also show the enablement state. Enabled commands start at boot. See the full table of | |
395 | possible enablement states — including the definition of <literal>masked</literal> — in the documentation | |
396 | for the <command>is-enabled</command> command. | |
397 | </para> | |
ac5e3a50 | 398 | |
e1fac8a6 ZJS |
399 | <para>The "Active:" line shows active state. The value is usually <literal>active</literal> or |
400 | <literal>inactive</literal>. Active could mean started, bound, plugged in, etc depending on the unit type. | |
401 | The unit could also be in process of changing states, reporting a state of <literal>activating</literal> or | |
402 | <literal>deactivating</literal>. A special <literal>failed</literal> state is entered when the service | |
403 | failed in some way, such as a crash, exiting with an error code or timing out. If the failed state is | |
404 | entered the cause will be logged for later reference.</para> | |
405 | </example> | |
ac5e3a50 | 406 | |
e1fac8a6 ZJS |
407 | </listitem> |
408 | </varlistentry> | |
409 | <varlistentry> | |
410 | <term><command>show</command> <optional><replaceable>PATTERN</replaceable>…|<replaceable>JOB</replaceable>…</optional></term> | |
4a6022f0 | 411 | |
e1fac8a6 ZJS |
412 | <listitem> |
413 | <para>Show properties of one or more units, jobs, or the manager itself. If no argument is specified, | |
414 | properties of the manager will be shown. If a unit name is specified, properties of the unit are shown, and | |
415 | if a job ID is specified, properties of the job are shown. By default, empty properties are suppressed. Use | |
416 | <option>--all</option> to show those too. To select specific properties to show, use | |
417 | <option>--property=</option>. This command is intended to be used whenever computer-parsable output is | |
418 | required. Use <command>status</command> if you are looking for formatted human-readable output.</para> | |
4a6022f0 | 419 | |
e1fac8a6 ZJS |
420 | <para>Many properties shown by <command>systemctl show</command> map directly to configuration settings of |
421 | the system and service manager and its unit files. Note that the properties shown by the command are | |
422 | generally more low-level, normalized versions of the original configuration settings and expose runtime | |
423 | state in addition to configuration. For example, properties shown for service units include the service's | |
424 | current main process identifier as <literal>MainPID</literal> (which is runtime state), and time settings | |
425 | are always exposed as properties ending in the <literal>…USec</literal> suffix even if a matching | |
426 | configuration options end in <literal>…Sec</literal>, because microseconds is the normalized time unit used | |
427 | by the system and service manager.</para> | |
428 | </listitem> | |
429 | </varlistentry> | |
430 | <varlistentry> | |
431 | <term><command>cat <replaceable>PATTERN</replaceable>…</command></term> | |
1ae17672 | 432 | |
e1fac8a6 ZJS |
433 | <listitem> |
434 | <para>Show backing files of one or more units. Prints the | |
435 | "fragment" and "drop-ins" (source files) of units. Each | |
436 | file is preceded by a comment which includes the file | |
437 | name. Note that this shows the contents of the backing files | |
438 | on disk, which may not match the system manager's | |
439 | understanding of these units if any unit files were | |
440 | updated on disk and the <command>daemon-reload</command> | |
441 | command wasn't issued since.</para> | |
442 | </listitem> | |
443 | </varlistentry> | |
444 | <varlistentry> | |
445 | <term><command>set-property <replaceable>UNIT</replaceable> <replaceable>PROPERTY</replaceable>=<replaceable>VALUE</replaceable>…</command></term> | |
1ae17672 | 446 | |
e1fac8a6 ZJS |
447 | <listitem> |
448 | <para>Set the specified unit properties at runtime where | |
449 | this is supported. This allows changing configuration | |
450 | parameter properties such as resource control settings at | |
451 | runtime. Not all properties may be changed at runtime, but | |
452 | many resource control settings (primarily those in | |
453 | <citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>) | |
454 | may. The changes are applied immediately, and stored on disk | |
455 | for future boots, unless <option>--runtime</option> is | |
456 | passed, in which case the settings only apply until the | |
457 | next reboot. The syntax of the property assignment follows | |
458 | closely the syntax of assignments in unit files.</para> | |
4a6022f0 | 459 | |
e1fac8a6 | 460 | <para>Example: <command>systemctl set-property foobar.service CPUWeight=200</command></para> |
4a6022f0 | 461 | |
e1fac8a6 ZJS |
462 | <para>If the specified unit appears to be inactive, the |
463 | changes will be only stored on disk as described | |
464 | previously hence they will be effective when the unit will | |
465 | be started.</para> | |
4a6022f0 | 466 | |
e1fac8a6 ZJS |
467 | <para>Note that this command allows changing multiple properties at the same time, which is |
468 | preferable over setting them individually.</para> | |
93a08841 | 469 | |
e1fac8a6 | 470 | <para>Example: <command>systemctl set-property foobar.service CPUWeight=200 MemoryMax=2G IPAccounting=yes</command></para> |
93a08841 | 471 | |
e1fac8a6 ZJS |
472 | <para>Like with unit file configuration settings, assigning an empty setting usually resets a |
473 | property to its defaults.</para> | |
adb6cd9b | 474 | |
e1fac8a6 ZJS |
475 | <para>Example: <command>systemctl set-property avahi-daemon.service IPAddressDeny=</command></para> |
476 | </listitem> | |
477 | </varlistentry> | |
4a6022f0 | 478 | |
e1fac8a6 ZJS |
479 | <varlistentry> |
480 | <term><command>help <replaceable>PATTERN</replaceable>…|<replaceable>PID</replaceable>…</command></term> | |
4a6022f0 | 481 | |
e1fac8a6 ZJS |
482 | <listitem> |
483 | <para>Show manual pages for one or more units, if | |
484 | available. If a PID is given, the manual pages for the unit | |
485 | the process belongs to are shown.</para> | |
486 | </listitem> | |
487 | </varlistentry> | |
bef19548 | 488 | |
e1fac8a6 ZJS |
489 | <varlistentry> |
490 | <term><command>reset-failed [<replaceable>PATTERN</replaceable>…]</command></term> | |
599b6322 | 491 | |
e1fac8a6 ZJS |
492 | <listitem> |
493 | <para>Reset the <literal>failed</literal> state of the specified units, or if no unit name is passed, reset | |
494 | the state of all units. When a unit fails in some way (i.e. process exiting with non-zero error code, | |
495 | terminating abnormally or timing out), it will automatically enter the <literal>failed</literal> state and | |
496 | its exit code and status is recorded for introspection by the administrator until the service is | |
497 | stopped/re-started or reset with this command.</para> | |
4a6022f0 | 498 | |
e1fac8a6 ZJS |
499 | <para>In addition to resetting the <literal>failed</literal> state of a unit it also resets various other |
500 | per-unit properties: the start rate limit counter of all unit types is reset to zero, as is the restart | |
501 | counter of service units. Thus, if a unit's start limit (as configured with | |
502 | <varname>StartLimitIntervalSec=</varname>/<varname>StartLimitBurst=</varname>) is hit and the unit refuses | |
503 | to be started again, use this command to make it startable again.</para> | |
504 | </listitem> | |
505 | </varlistentry> | |
4a6022f0 | 506 | |
e1fac8a6 ZJS |
507 | <varlistentry> |
508 | <term> | |
509 | <command>list-dependencies</command> | |
510 | <optional><replaceable>UNIT</replaceable></optional> | |
511 | </term> | |
4a6022f0 | 512 | |
e1fac8a6 ZJS |
513 | <listitem> |
514 | <para>Shows units required and wanted by the specified | |
515 | unit. This recursively lists units following the | |
516 | <varname>Requires=</varname>, | |
517 | <varname>Requisite=</varname>, | |
518 | <varname>ConsistsOf=</varname>, | |
519 | <varname>Wants=</varname>, <varname>BindsTo=</varname> | |
520 | dependencies. If no unit is specified, | |
521 | <filename>default.target</filename> is implied.</para> | |
4a6022f0 | 522 | |
e1fac8a6 ZJS |
523 | <para>By default, only target units are recursively |
524 | expanded. When <option>--all</option> is passed, all other | |
525 | units are recursively expanded as well.</para> | |
4a6022f0 | 526 | |
e1fac8a6 ZJS |
527 | <para>Options <option>--reverse</option>, |
528 | <option>--after</option>, <option>--before</option> | |
529 | may be used to change what types of dependencies | |
530 | are shown.</para> | |
4a6022f0 | 531 | |
e1fac8a6 ZJS |
532 | <para>Note that this command only lists units currently loaded into memory by the service manager. In |
533 | particular, this command is not suitable to get a comprehensive list at all reverse dependencies on a | |
534 | specific unit, as it won't list the dependencies declared by units currently not loaded.</para> | |
535 | </listitem> | |
536 | </varlistentry> | |
537 | </variablelist> | |
538 | </refsect2> | |
4a6022f0 | 539 | |
e1fac8a6 ZJS |
540 | <refsect2> |
541 | <title>Unit File Commands</title> | |
4a6022f0 | 542 | |
e1fac8a6 ZJS |
543 | <variablelist> |
544 | <varlistentry> | |
545 | <term><command>list-unit-files</command> <optional><replaceable>PATTERN…</replaceable></optional></term> | |
4a6022f0 | 546 | |
e1fac8a6 ZJS |
547 | <listitem> |
548 | <para>List unit files installed on the system, in combination with their enablement state (as reported by | |
549 | <command>is-enabled</command>). If one or more <replaceable>PATTERN</replaceable>s are specified, only unit | |
550 | files whose name matches one of them are shown (patterns matching unit file system paths are not | |
551 | supported).</para> | |
552 | </listitem> | |
553 | </varlistentry> | |
4a6022f0 | 554 | |
e1fac8a6 ZJS |
555 | <varlistentry> |
556 | <term><command>enable <replaceable>UNIT</replaceable>…</command></term> | |
557 | <term><command>enable <replaceable>PATH</replaceable>…</command></term> | |
4a6022f0 | 558 | |
e1fac8a6 ZJS |
559 | <listitem> |
560 | <para>Enable one or more units or unit instances. This will create a set of symlinks, as encoded in the | |
561 | <literal>[Install]</literal> sections of the indicated unit files. After the symlinks have been created, | |
562 | the system manager configuration is reloaded (in a way equivalent to <command>daemon-reload</command>), in | |
563 | order to ensure the changes are taken into account immediately. Note that this does | |
564 | <emphasis>not</emphasis> have the effect of also starting any of the units being enabled. If this is | |
565 | desired, combine this command with the <option>--now</option> switch, or invoke <command>start</command> | |
566 | with appropriate arguments later. Note that in case of unit instance enablement (i.e. enablement of units of | |
567 | the form <filename>foo@bar.service</filename>), symlinks named the same as instances are created in the | |
568 | unit configuration directory, however they point to the single template unit file they are instantiated | |
569 | from.</para> | |
4a6022f0 | 570 | |
e1fac8a6 ZJS |
571 | <para>This command expects either valid unit names (in which case various unit file directories are |
572 | automatically searched for unit files with appropriate names), or absolute paths to unit files (in which | |
573 | case these files are read directly). If a specified unit file is located outside of the usual unit file | |
574 | directories, an additional symlink is created, linking it into the unit configuration path, thus ensuring | |
575 | it is found when requested by commands such as <command>start</command>. The file system where the linked | |
576 | unit files are located must be accessible when systemd is started (e.g. anything underneath | |
577 | <filename>/home</filename> or <filename>/var</filename> is not allowed, unless those directories are | |
578 | located on the root file system).</para> | |
4a6022f0 | 579 | |
e1fac8a6 ZJS |
580 | <para>This command will print the file system operations executed. This output may be suppressed by passing |
581 | <option>--quiet</option>. | |
582 | </para> | |
8c8208cb | 583 | |
e1fac8a6 ZJS |
584 | <para>Note that this operation creates only the symlinks suggested in the <literal>[Install]</literal> |
585 | section of the unit files. While this command is the recommended way to manipulate the unit configuration | |
586 | directory, the administrator is free to make additional changes manually by placing or removing symlinks | |
587 | below this directory. This is particularly useful to create configurations that deviate from the suggested | |
588 | default installation. In this case, the administrator must make sure to invoke | |
589 | <command>daemon-reload</command> manually as necessary, in order to ensure the changes are taken into | |
590 | account. | |
591 | </para> | |
8c8208cb | 592 | |
e1fac8a6 ZJS |
593 | <para>Enabling units should not be confused with starting (activating) units, as done by the |
594 | <command>start</command> command. Enabling and starting units is orthogonal: units may be enabled without | |
595 | being started and started without being enabled. Enabling simply hooks the unit into various suggested | |
596 | places (for example, so that the unit is automatically started on boot or when a particular kind of | |
597 | hardware is plugged in). Starting actually spawns the daemon process (in case of service units), or binds | |
598 | the socket (in case of socket units), and so on.</para> | |
4a6022f0 | 599 | |
e1fac8a6 ZJS |
600 | <para>Depending on whether <option>--system</option>, <option>--user</option>, <option>--runtime</option>, |
601 | or <option>--global</option> is specified, this enables the unit for the system, for the calling user only, | |
602 | for only this boot of the system, or for all future logins of all users. Note that in the last case, no | |
603 | systemd daemon configuration is reloaded.</para> | |
4a6022f0 | 604 | |
e1fac8a6 ZJS |
605 | <para>Using <command>enable</command> on masked units is not supported and results in an error.</para> |
606 | </listitem> | |
607 | </varlistentry> | |
39c38ce1 | 608 | |
e1fac8a6 ZJS |
609 | <varlistentry> |
610 | <term><command>disable <replaceable>UNIT</replaceable>…</command></term> | |
4a6022f0 | 611 | |
e1fac8a6 ZJS |
612 | <listitem> |
613 | <para>Disables one or more units. This removes all symlinks to the unit files backing the specified units | |
614 | from the unit configuration directory, and hence undoes any changes made by <command>enable</command> or | |
615 | <command>link</command>. Note that this removes <emphasis>all</emphasis> symlinks to matching unit files, | |
616 | including manually created symlinks, and not just those actually created by <command>enable</command> or | |
617 | <command>link</command>. Note that while <command>disable</command> undoes the effect of | |
618 | <command>enable</command>, the two commands are otherwise not symmetric, as <command>disable</command> may | |
619 | remove more symlinks than a prior <command>enable</command> invocation of the same unit created.</para> | |
9ef15026 | 620 | |
e1fac8a6 | 621 | <para>This command expects valid unit names only, it does not accept paths to unit files.</para> |
9ef15026 | 622 | |
e1fac8a6 ZJS |
623 | <para>In addition to the units specified as arguments, all units are disabled that are listed in the |
624 | <varname>Also=</varname> setting contained in the <literal>[Install]</literal> section of any of the unit | |
625 | files being operated on.</para> | |
57ab2eab | 626 | |
e1fac8a6 ZJS |
627 | <para>This command implicitly reloads the system manager configuration after completing the operation. Note |
628 | that this command does not implicitly stop the units that are being disabled. If this is desired, either | |
629 | combine this command with the <option>--now</option> switch, or invoke the <command>stop</command> command | |
630 | with appropriate arguments later.</para> | |
57ab2eab | 631 | |
e1fac8a6 ZJS |
632 | <para>This command will print information about the file system operations (symlink removals) |
633 | executed. This output may be suppressed by passing <option>--quiet</option>. | |
634 | </para> | |
4a6022f0 | 635 | |
e1fac8a6 ZJS |
636 | <para>This command honors <option>--system</option>, <option>--user</option>, <option>--runtime</option> |
637 | and <option>--global</option> in a similar way as <command>enable</command>.</para> | |
638 | </listitem> | |
639 | </varlistentry> | |
4a6022f0 | 640 | |
e1fac8a6 ZJS |
641 | <varlistentry> |
642 | <term><command>reenable <replaceable>UNIT</replaceable>…</command></term> | |
4a6022f0 | 643 | |
e1fac8a6 ZJS |
644 | <listitem> |
645 | <para>Reenable one or more units, as specified on the command line. This is a combination of | |
646 | <command>disable</command> and <command>enable</command> and is useful to reset the symlinks a unit file is | |
647 | enabled with to the defaults configured in its <literal>[Install]</literal> section. This command expects | |
648 | a unit name only, it does not accept paths to unit files.</para> | |
649 | </listitem> | |
650 | </varlistentry> | |
4a6022f0 | 651 | |
e1fac8a6 ZJS |
652 | <varlistentry> |
653 | <term><command>preset <replaceable>UNIT</replaceable>…</command></term> | |
a330b376 | 654 | |
e1fac8a6 ZJS |
655 | <listitem> |
656 | <para>Reset the enable/disable status one or more unit files, as specified on | |
657 | the command line, to the defaults configured in the preset policy files. This | |
658 | has the same effect as <command>disable</command> or | |
659 | <command>enable</command>, depending how the unit is listed in the preset | |
660 | files.</para> | |
4a6022f0 | 661 | |
e1fac8a6 ZJS |
662 | <para>Use <option>--preset-mode=</option> to control whether units shall be |
663 | enabled and disabled, or only enabled, or only disabled.</para> | |
d309c1c3 | 664 | |
e1fac8a6 ZJS |
665 | <para>If the unit carries no install information, it will be silently ignored |
666 | by this command. <replaceable>UNIT</replaceable> must be the real unit name, | |
667 | any alias names are ignored silently.</para> | |
d309c1c3 | 668 | |
e1fac8a6 ZJS |
669 | <para>For more information on the preset policy format, see |
670 | <citerefentry><refentrytitle>systemd.preset</refentrytitle><manvolnum>5</manvolnum></citerefentry>. | |
671 | For more information on the concept of presets, please consult the | |
672 | <ulink url="https://www.freedesktop.org/wiki/Software/systemd/Preset">Preset</ulink> | |
673 | document.</para> | |
674 | </listitem> | |
675 | </varlistentry> | |
4a6022f0 | 676 | |
e1fac8a6 ZJS |
677 | <varlistentry> |
678 | <term><command>preset-all</command></term> | |
4a6022f0 | 679 | |
e1fac8a6 ZJS |
680 | <listitem> |
681 | <para>Resets all installed unit files to the defaults | |
682 | configured in the preset policy file (see above).</para> | |
4a6022f0 | 683 | |
e1fac8a6 ZJS |
684 | <para>Use <option>--preset-mode=</option> to control |
685 | whether units shall be enabled and disabled, or only | |
686 | enabled, or only disabled.</para> | |
687 | </listitem> | |
688 | </varlistentry> | |
4a6022f0 | 689 | |
27722f96 | 690 | <varlistentry> |
e1fac8a6 | 691 | <term><command>is-enabled <replaceable>UNIT</replaceable>…</command></term> |
4a6022f0 | 692 | |
27722f96 | 693 | <listitem> |
e1fac8a6 ZJS |
694 | <para>Checks whether any of the specified unit files are |
695 | enabled (as with <command>enable</command>). Returns an | |
696 | exit code of 0 if at least one is enabled, non-zero | |
697 | otherwise. Prints the current enable status (see table). | |
698 | To suppress this output, use <option>--quiet</option>. | |
699 | To show installation targets, use <option>--full</option>. | |
700 | </para> | |
6fdbb3c8 | 701 | |
e1fac8a6 ZJS |
702 | <table> |
703 | <title> | |
704 | <command>is-enabled</command> output | |
705 | </title> | |
6fdbb3c8 | 706 | |
e1fac8a6 ZJS |
707 | <tgroup cols='3'> |
708 | <thead> | |
709 | <row> | |
710 | <entry>Name</entry> | |
711 | <entry>Description</entry> | |
712 | <entry>Exit Code</entry> | |
713 | </row> | |
714 | </thead> | |
715 | <tbody> | |
716 | <row> | |
717 | <entry><literal>enabled</literal></entry> | |
718 | <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> | |
719 | <entry morerows='1'>0</entry> | |
720 | </row> | |
721 | <row> | |
722 | <entry><literal>enabled-runtime</literal></entry> | |
723 | </row> | |
724 | <row> | |
725 | <entry><literal>linked</literal></entry> | |
726 | <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> | |
727 | <entry morerows='1'>> 0</entry> | |
728 | </row> | |
729 | <row> | |
730 | <entry><literal>linked-runtime</literal></entry> | |
731 | </row> | |
732 | <row> | |
733 | <entry><literal>masked</literal></entry> | |
734 | <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> | |
735 | <entry morerows='1'>> 0</entry> | |
736 | </row> | |
737 | <row> | |
738 | <entry><literal>masked-runtime</literal></entry> | |
739 | </row> | |
740 | <row> | |
741 | <entry><literal>static</literal></entry> | |
742 | <entry>The unit file is not enabled, and has no provisions for enabling in the <literal>[Install]</literal> unit file section.</entry> | |
743 | <entry>0</entry> | |
744 | </row> | |
745 | <row> | |
746 | <entry><literal>indirect</literal></entry> | |
747 | <entry>The unit file itself is not enabled, but it has a non-empty <varname>Also=</varname> setting in the <literal>[Install]</literal> 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 file, an instance different than the one specified in <varname>DefaultInstance=</varname> is enabled.</entry> | |
748 | <entry>0</entry> | |
749 | </row> | |
750 | <row> | |
751 | <entry><literal>disabled</literal></entry> | |
752 | <entry>The unit file is not enabled, but contains an <literal>[Install]</literal> section with installation instructions.</entry> | |
753 | <entry>> 0</entry> | |
754 | </row> | |
755 | <row> | |
756 | <entry><literal>generated</literal></entry> | |
757 | <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> | |
758 | <entry>0</entry> | |
759 | </row> | |
760 | <row> | |
761 | <entry><literal>transient</literal></entry> | |
762 | <entry>The unit file has been created dynamically with the runtime API. Transient units may not be enabled.</entry> | |
763 | <entry>0</entry> | |
764 | </row> | |
765 | <row> | |
766 | <entry><literal>bad</literal></entry> | |
767 | <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> | |
768 | <entry>> 0</entry> | |
769 | </row> | |
770 | </tbody> | |
771 | </tgroup> | |
772 | </table> | |
6fdbb3c8 | 773 | |
27722f96 LN |
774 | </listitem> |
775 | </varlistentry> | |
991f2a39 | 776 | |
27722f96 | 777 | <varlistentry> |
e1fac8a6 | 778 | <term><command>mask <replaceable>UNIT</replaceable>…</command></term> |
27722f96 LN |
779 | |
780 | <listitem> | |
e1fac8a6 ZJS |
781 | <para>Mask one or more units, as specified on the command line. This will link these unit files to |
782 | <filename>/dev/null</filename>, making it impossible to start them. This is a stronger version of | |
783 | <command>disable</command>, since it prohibits all kinds of activation of the unit, including enablement | |
784 | and manual activation. Use this option with care. This honors the <option>--runtime</option> option to only | |
785 | mask temporarily until the next reboot of the system. The <option>--now</option> option may be used to | |
786 | ensure that the units are also stopped. This command expects valid unit names only, it does not accept unit | |
787 | file paths.</para> | |
27722f96 LN |
788 | </listitem> |
789 | </varlistentry> | |
790 | ||
cbb76c29 | 791 | <varlistentry> |
e1fac8a6 | 792 | <term><command>unmask <replaceable>UNIT</replaceable>…</command></term> |
cbb76c29 LP |
793 | |
794 | <listitem> | |
e1fac8a6 ZJS |
795 | <para>Unmask one or more unit files, as specified on the command line. This will undo the effect of |
796 | <command>mask</command>. This command expects valid unit names only, it does not accept unit file | |
797 | paths.</para> | |
798 | </listitem> | |
799 | </varlistentry> | |
cbb76c29 | 800 | |
e1fac8a6 ZJS |
801 | <varlistentry> |
802 | <term><command>link <replaceable>PATH</replaceable>…</command></term> | |
ccdda955 | 803 | |
e1fac8a6 ZJS |
804 | <listitem> |
805 | <para>Link a unit file that is not in the unit file search paths into the unit file search path. This | |
806 | command expects an absolute path to a unit file. The effect of this may be undone with | |
807 | <command>disable</command>. The effect of this command is that a unit file is made available for commands | |
808 | such as <command>start</command>, even though it is not installed directly in the unit search path. The | |
809 | file system where the linked unit files are located must be accessible when systemd is started | |
810 | (e.g. anything underneath <filename>/home</filename> or <filename>/var</filename> is not allowed, unless | |
811 | those directories are located on the root file system).</para> | |
cbb76c29 LP |
812 | </listitem> |
813 | </varlistentry> | |
814 | ||
27722f96 | 815 | <varlistentry> |
e1fac8a6 | 816 | <term><command>revert <replaceable>UNIT</replaceable>…</command></term> |
27722f96 LN |
817 | |
818 | <listitem> | |
e1fac8a6 ZJS |
819 | <para>Revert one or more unit files to their vendor versions. This command removes drop-in configuration |
820 | files that modify the specified units, as well as any user-configured unit file that overrides a matching | |
821 | vendor supplied unit file. Specifically, for a unit <literal>foo.service</literal> the matching directories | |
822 | <literal>foo.service.d/</literal> with all their contained files are removed, both below the persistent and | |
823 | runtime configuration directories (i.e. below <filename>/etc/systemd/system</filename> and | |
824 | <filename>/run/systemd/system</filename>); if the unit file has a vendor-supplied version (i.e. a unit file | |
825 | located below <filename>/usr</filename>) any matching persistent or runtime unit file that overrides it is | |
826 | removed, too. Note that if a unit file has no vendor-supplied version (i.e. is only defined below | |
827 | <filename>/etc/systemd/system</filename> or <filename>/run/systemd/system</filename>, but not in a unit | |
828 | file stored below <filename>/usr</filename>), then it is not removed. Also, if a unit is masked, it is | |
829 | unmasked.</para> | |
830 | ||
831 | <para>Effectively, this command may be used to undo all changes made with <command>systemctl | |
832 | edit</command>, <command>systemctl set-property</command> and <command>systemctl mask</command> and puts | |
833 | the original unit file with its settings back in effect.</para> | |
27722f96 LN |
834 | </listitem> |
835 | </varlistentry> | |
e1fac8a6 | 836 | |
27722f96 | 837 | <varlistentry> |
e1fac8a6 ZJS |
838 | <term><command>add-wants <replaceable>TARGET</replaceable> |
839 | <replaceable>UNIT</replaceable>…</command></term> | |
840 | <term><command>add-requires <replaceable>TARGET</replaceable> | |
841 | <replaceable>UNIT</replaceable>…</command></term> | |
27722f96 LN |
842 | |
843 | <listitem> | |
e1fac8a6 ZJS |
844 | <para>Adds <literal>Wants=</literal> or <literal>Requires=</literal> |
845 | dependencies, respectively, to the specified | |
846 | <replaceable>TARGET</replaceable> for one or more units. </para> | |
847 | ||
848 | <para>This command honors <option>--system</option>, | |
849 | <option>--user</option>, <option>--runtime</option> and | |
850 | <option>--global</option> in a way similar to | |
851 | <command>enable</command>.</para> | |
4f0acdb3 | 852 | |
27722f96 LN |
853 | </listitem> |
854 | </varlistentry> | |
e1fac8a6 | 855 | |
27722f96 | 856 | <varlistentry> |
e1fac8a6 | 857 | <term><command>edit <replaceable>UNIT</replaceable>…</command></term> |
27722f96 LN |
858 | |
859 | <listitem> | |
e1fac8a6 ZJS |
860 | <para>Edit a drop-in snippet or a whole replacement file if |
861 | <option>--full</option> is specified, to extend or override the | |
862 | specified unit.</para> | |
27722f96 | 863 | |
e1fac8a6 ZJS |
864 | <para>Depending on whether <option>--system</option> (the default), |
865 | <option>--user</option>, or <option>--global</option> is specified, | |
866 | this command creates a drop-in file for each unit either for the system, | |
867 | for the calling user, or for all futures logins of all users. Then, | |
868 | the editor (see the "Environment" section below) is invoked on | |
869 | temporary files which will be written to the real location if the | |
870 | editor exits successfully.</para> | |
27722f96 | 871 | |
e1fac8a6 ZJS |
872 | <para>If <option>--full</option> is specified, this will copy the |
873 | original units instead of creating drop-in files.</para> | |
27722f96 | 874 | |
e1fac8a6 ZJS |
875 | <para>If <option>--force</option> is specified and any units do |
876 | not already exist, new unit files will be opened for editing.</para> | |
c4f2aaa4 | 877 | |
e1fac8a6 ZJS |
878 | <para>If <option>--runtime</option> is specified, the changes will |
879 | be made temporarily in <filename>/run</filename> and they will be | |
880 | lost on the next reboot.</para> | |
881 | ||
882 | <para>If the temporary file is empty upon exit, the modification of | |
883 | the related unit is canceled.</para> | |
884 | ||
885 | <para>After the units have been edited, systemd configuration is | |
886 | reloaded (in a way that is equivalent to <command>daemon-reload</command>). | |
887 | </para> | |
888 | ||
889 | <para>Note that this command cannot be used to remotely edit units | |
890 | and that you cannot temporarily edit units which are in | |
891 | <filename>/etc</filename>, since they take precedence over | |
892 | <filename>/run</filename>.</para> | |
27722f96 LN |
893 | </listitem> |
894 | </varlistentry> | |
e1fac8a6 | 895 | |
27722f96 | 896 | <varlistentry> |
e1fac8a6 | 897 | <term><command>get-default</command></term> |
27722f96 LN |
898 | |
899 | <listitem> | |
e1fac8a6 ZJS |
900 | <para>Return the default target to boot into. This returns |
901 | the target unit name <filename>default.target</filename> | |
902 | is aliased (symlinked) to.</para> | |
27722f96 LN |
903 | </listitem> |
904 | </varlistentry> | |
e1fac8a6 | 905 | |
27722f96 | 906 | <varlistentry> |
e1fac8a6 | 907 | <term><command>set-default <replaceable>TARGET</replaceable></command></term> |
27722f96 LN |
908 | |
909 | <listitem> | |
e1fac8a6 ZJS |
910 | <para>Set the default target to boot into. This sets |
911 | (symlinks) the <filename>default.target</filename> alias | |
912 | to the given target unit.</para> | |
27722f96 LN |
913 | </listitem> |
914 | </varlistentry> | |
e1fac8a6 ZJS |
915 | |
916 | </variablelist> | |
917 | </refsect2> | |
918 | ||
919 | <refsect2> | |
920 | <title>Machine Commands</title> | |
921 | ||
922 | <variablelist> | |
27722f96 | 923 | <varlistentry> |
e1fac8a6 | 924 | <term><command>list-machines</command> <optional><replaceable>PATTERN</replaceable>…</optional></term> |
27722f96 LN |
925 | |
926 | <listitem> | |
e1fac8a6 ZJS |
927 | <para>List the host and all running local containers with |
928 | their state. If one or more | |
929 | <replaceable>PATTERN</replaceable>s are specified, only | |
930 | containers matching one of them are shown. | |
931 | </para> | |
27722f96 LN |
932 | </listitem> |
933 | </varlistentry> | |
e1fac8a6 ZJS |
934 | </variablelist> |
935 | </refsect2> | |
936 | ||
937 | <refsect2> | |
938 | <title>Job Commands</title> | |
939 | ||
940 | <variablelist> | |
27722f96 | 941 | <varlistentry> |
e1fac8a6 | 942 | <term><command>list-jobs <optional><replaceable>PATTERN…</replaceable></optional></command></term> |
27722f96 LN |
943 | |
944 | <listitem> | |
e1fac8a6 ZJS |
945 | <para>List jobs that are in progress. If one or more |
946 | <replaceable>PATTERN</replaceable>s are specified, only | |
947 | jobs for units matching one of them are shown.</para> | |
27722f96 | 948 | |
e1fac8a6 ZJS |
949 | <para>When combined with <option>--after</option> or <option>--before</option> the list is augmented with |
950 | information on which other job each job is waiting for, and which other jobs are waiting for it, see | |
951 | above.</para> | |
27722f96 LN |
952 | </listitem> |
953 | </varlistentry> | |
954 | <varlistentry> | |
e1fac8a6 | 955 | <term><command>cancel <replaceable>JOB</replaceable>…</command></term> |
27722f96 LN |
956 | |
957 | <listitem> | |
e1fac8a6 ZJS |
958 | <para>Cancel one or more jobs specified on the command line |
959 | by their numeric job IDs. If no job ID is specified, cancel | |
960 | all pending jobs.</para> | |
27722f96 LN |
961 | </listitem> |
962 | </varlistentry> | |
e1fac8a6 ZJS |
963 | </variablelist> |
964 | </refsect2> | |
965 | ||
966 | <refsect2> | |
967 | <title>Environment Commands</title> | |
968 | ||
969 | <variablelist> | |
8c8208cb | 970 | <varlistentry> |
e1fac8a6 | 971 | <term><command>show-environment</command></term> |
8c8208cb LP |
972 | |
973 | <listitem> | |
e1fac8a6 ZJS |
974 | <para>Dump the systemd manager environment block. This is the environment |
975 | block that is passed to all processes the manager spawns. The environment | |
976 | block will be dumped in straight-forward form suitable for sourcing into | |
977 | most shells. If no special characters or whitespace is present in the variable | |
978 | values, no escaping is performed, and the assignments have the form | |
979 | <literal>VARIABLE=value</literal>. If whitespace or characters which have | |
980 | special meaning to the shell are present, dollar-single-quote escaping is | |
981 | used, and assignments have the form <literal>VARIABLE=$'value'</literal>. | |
982 | This syntax is known to be supported by | |
983 | <citerefentry project='die-net'><refentrytitle>bash</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
984 | <citerefentry project='die-net'><refentrytitle>zsh</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
985 | <citerefentry project='die-net'><refentrytitle>ksh</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
986 | and | |
987 | <citerefentry project='die-net'><refentrytitle>busybox</refentrytitle><manvolnum>1</manvolnum></citerefentry>'s | |
988 | <citerefentry project='die-net'><refentrytitle>ash</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
989 | but not | |
990 | <citerefentry project='die-net'><refentrytitle>dash</refentrytitle><manvolnum>1</manvolnum></citerefentry> | |
991 | or | |
992 | <citerefentry project='die-net'><refentrytitle>fish</refentrytitle><manvolnum>1</manvolnum></citerefentry>. | |
993 | </para> | |
8c8208cb LP |
994 | </listitem> |
995 | </varlistentry> | |
27722f96 | 996 | <varlistentry> |
e1fac8a6 | 997 | <term><command>set-environment <replaceable>VARIABLE=VALUE</replaceable>…</command></term> |
27722f96 LN |
998 | |
999 | <listitem> | |
e1fac8a6 ZJS |
1000 | <para>Set one or more systemd manager environment variables, |
1001 | as specified on the command line.</para> | |
27722f96 LN |
1002 | </listitem> |
1003 | </varlistentry> | |
1004 | <varlistentry> | |
e1fac8a6 | 1005 | <term><command>unset-environment <replaceable>VARIABLE</replaceable>…</command></term> |
27722f96 LN |
1006 | |
1007 | <listitem> | |
e1fac8a6 ZJS |
1008 | <para>Unset one or more systemd manager environment |
1009 | variables. If only a variable name is specified, it will be | |
1010 | removed regardless of its value. If a variable and a value | |
1011 | are specified, the variable is only removed if it has the | |
1012 | specified value.</para> | |
27722f96 LN |
1013 | </listitem> |
1014 | </varlistentry> | |
1015 | <varlistentry> | |
e1fac8a6 ZJS |
1016 | <term> |
1017 | <command>import-environment</command> | |
1018 | <optional><replaceable>VARIABLE…</replaceable></optional> | |
1019 | </term> | |
27722f96 LN |
1020 | |
1021 | <listitem> | |
e1fac8a6 ZJS |
1022 | <para>Import all, one or more environment variables set on |
1023 | the client into the systemd manager environment block. If | |
1024 | no arguments are passed, the entire environment block is | |
1025 | imported. Otherwise, a list of one or more environment | |
1026 | variable names should be passed, whose client-side values | |
1027 | are then imported into the manager's environment | |
1028 | block.</para> | |
27722f96 LN |
1029 | </listitem> |
1030 | </varlistentry> | |
e1fac8a6 ZJS |
1031 | </variablelist> |
1032 | </refsect2> | |
1033 | ||
1034 | <refsect2> | |
38fcb7f7 | 1035 | <title>Manager State Commands</title> |
e1fac8a6 ZJS |
1036 | |
1037 | <variablelist> | |
27722f96 | 1038 | <varlistentry> |
e1fac8a6 | 1039 | <term><command>daemon-reload</command></term> |
27722f96 LN |
1040 | |
1041 | <listitem> | |
e1fac8a6 ZJS |
1042 | <para>Reload the systemd manager configuration. This will |
1043 | rerun all generators (see | |
1044 | <citerefentry><refentrytitle>systemd.generator</refentrytitle><manvolnum>7</manvolnum></citerefentry>), | |
1045 | reload all unit files, and recreate the entire dependency | |
1046 | tree. While the daemon is being reloaded, all sockets | |
1047 | systemd listens on behalf of user configuration will stay | |
1048 | accessible.</para> | |
33d2308c | 1049 | |
e1fac8a6 ZJS |
1050 | <para>This command should not be confused with the |
1051 | <command>reload</command> command.</para> | |
27722f96 LN |
1052 | </listitem> |
1053 | </varlistentry> | |
38fcb7f7 | 1054 | |
e93c33d4 | 1055 | <varlistentry> |
e1fac8a6 | 1056 | <term><command>daemon-reexec</command></term> |
27722f96 | 1057 | |
e93c33d4 | 1058 | <listitem> |
e1fac8a6 ZJS |
1059 | <para>Reexecute the systemd manager. This will serialize the |
1060 | manager state, reexecute the process and deserialize the | |
1061 | state again. This command is of little use except for | |
1062 | debugging and package upgrades. Sometimes, it might be | |
1063 | helpful as a heavy-weight <command>daemon-reload</command>. | |
1064 | While the daemon is being reexecuted, all sockets systemd listening | |
1065 | on behalf of user configuration will stay accessible. | |
1066 | </para> | |
e93c33d4 SL |
1067 | </listitem> |
1068 | </varlistentry> | |
38fcb7f7 ZJS |
1069 | |
1070 | <varlistentry> | |
1071 | <term><command>log-level</command> [<replaceable>LEVEL</replaceable>]</term> | |
1072 | ||
1073 | <listitem><para>If no argument is given, print the current log level of the manager. If an | |
1074 | optional argument <replaceable>LEVEL</replaceable> is provided, then the command changes the | |
1075 | current log level of the manager to <replaceable>LEVEL</replaceable> (accepts the same values as | |
1076 | <option>--log-level=</option> described in | |
1077 | <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>). | |
1078 | </para></listitem> | |
1079 | </varlistentry> | |
1080 | ||
1081 | <varlistentry> | |
1082 | <term><command>log-target</command> [<replaceable>TARGET</replaceable>]</term> | |
1083 | ||
1084 | <listitem><para>If no argument is given, print the current log target of the manager. If an | |
1085 | optional argument <replaceable>TARGET</replaceable> is provided, then the command changes the | |
1086 | current log target of the manager to <replaceable>TARGET</replaceable> (accepts the same values as | |
1087 | <option>--log-target=</option>, described in | |
1088 | <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>). | |
1089 | </para></listitem> | |
1090 | </varlistentry> | |
6ab86319 ZJS |
1091 | |
1092 | <varlistentry> | |
1093 | <term><command>service-watchdogs</command> [yes|no]</term> | |
1094 | ||
1095 | <listitem><para>If no argument is given, print the current state of service runtime watchdogs of | |
1096 | the manager. If an optional boolean argument is provided, then globally enables or disables the | |
1097 | service runtime watchdogs (<option>WatchdogSec=</option>) and emergency actions (e.g. | |
1098 | <option>OnFailure=</option> or <option>StartLimitAction=</option>); see | |
1099 | <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>. | |
1100 | The hardware watchdog is not affected by this setting.</para></listitem> | |
1101 | </varlistentry> | |
e1fac8a6 ZJS |
1102 | </variablelist> |
1103 | </refsect2> | |
27722f96 | 1104 | |
e1fac8a6 ZJS |
1105 | <refsect2> |
1106 | <title>System Commands</title> | |
e9fd88f2 | 1107 | |
e1fac8a6 ZJS |
1108 | <variablelist> |
1109 | <varlistentry> | |
1110 | <term><command>is-system-running</command></term> | |
5b792edb | 1111 | |
e1fac8a6 ZJS |
1112 | <listitem> |
1113 | <para>Checks whether the system is operational. This | |
1114 | returns success (exit code 0) when the system is fully up | |
1115 | and running, specifically not in startup, shutdown or | |
1116 | maintenance mode, and with no failed services. Failure is | |
1117 | returned otherwise (exit code non-zero). In addition, the | |
1118 | current state is printed in a short string to standard | |
1119 | output, see the table below. Use <option>--quiet</option> to | |
1120 | suppress this output.</para> | |
5b792edb | 1121 | |
e1fac8a6 ZJS |
1122 | <para>Use <option>--wait</option> to wait until the boot |
1123 | process is completed before printing the current state and | |
1124 | returning the appropriate error status. If <option>--wait</option> | |
1125 | is in use, states <varname>initializing</varname> or | |
1126 | <varname>starting</varname> will not be reported, instead | |
1127 | the command will block until a later state (such as | |
1128 | <varname>running</varname> or <varname>degraded</varname>) | |
1129 | is reached.</para> | |
5b792edb | 1130 | |
e1fac8a6 ZJS |
1131 | <table> |
1132 | <title><command>is-system-running</command> output</title> | |
1133 | <tgroup cols='3'> | |
1134 | <colspec colname='name'/> | |
1135 | <colspec colname='description'/> | |
1136 | <colspec colname='exit-code'/> | |
1137 | <thead> | |
1138 | <row> | |
1139 | <entry>Name</entry> | |
1140 | <entry>Description</entry> | |
1141 | <entry>Exit Code</entry> | |
1142 | </row> | |
1143 | </thead> | |
1144 | <tbody> | |
1145 | <row> | |
1146 | <entry><varname>initializing</varname></entry> | |
1147 | <entry><para>Early bootup, before | |
1148 | <filename>basic.target</filename> is reached | |
1149 | or the <varname>maintenance</varname> state entered. | |
1150 | </para></entry> | |
1151 | <entry>> 0</entry> | |
1152 | </row> | |
1153 | <row> | |
1154 | <entry><varname>starting</varname></entry> | |
1155 | <entry><para>Late bootup, before the job queue | |
1156 | becomes idle for the first time, or one of the | |
1157 | rescue targets are reached.</para></entry> | |
1158 | <entry>> 0</entry> | |
1159 | </row> | |
1160 | <row> | |
1161 | <entry><varname>running</varname></entry> | |
1162 | <entry><para>The system is fully | |
1163 | operational.</para></entry> | |
1164 | <entry>0</entry> | |
1165 | </row> | |
1166 | <row> | |
1167 | <entry><varname>degraded</varname></entry> | |
1168 | <entry><para>The system is operational but one or more | |
1169 | units failed.</para></entry> | |
1170 | <entry>> 0</entry> | |
1171 | </row> | |
1172 | <row> | |
1173 | <entry><varname>maintenance</varname></entry> | |
1174 | <entry><para>The rescue or emergency target is | |
1175 | active.</para></entry> | |
1176 | <entry>> 0</entry> | |
1177 | </row> | |
1178 | <row> | |
1179 | <entry><varname>stopping</varname></entry> | |
1180 | <entry><para>The manager is shutting | |
1181 | down.</para></entry> | |
1182 | <entry>> 0</entry> | |
1183 | </row> | |
1184 | <row> | |
1185 | <entry><varname>offline</varname></entry> | |
1186 | <entry><para>The manager is not | |
1187 | running. Specifically, this is the operational | |
1188 | state if an incompatible program is running as | |
1189 | system manager (PID 1).</para></entry> | |
1190 | <entry>> 0</entry> | |
1191 | </row> | |
1192 | <row> | |
1193 | <entry><varname>unknown</varname></entry> | |
1194 | <entry><para>The operational state could not be | |
1195 | determined, due to lack of resources or another | |
1196 | error cause.</para></entry> | |
1197 | <entry>> 0</entry> | |
1198 | </row> | |
1199 | </tbody> | |
1200 | </tgroup> | |
1201 | </table> | |
27722f96 LN |
1202 | </listitem> |
1203 | </varlistentry> | |
1204 | ||
1205 | <varlistentry> | |
e1fac8a6 | 1206 | <term><command>default</command></term> |
27722f96 LN |
1207 | |
1208 | <listitem> | |
e1fac8a6 ZJS |
1209 | <para>Enter default mode. This is equivalent to <command>systemctl isolate default.target</command>. This |
1210 | operation is blocking by default, use <option>--no-block</option> to request asynchronous behavior.</para> | |
27722f96 LN |
1211 | </listitem> |
1212 | </varlistentry> | |
1213 | ||
1214 | <varlistentry> | |
e1fac8a6 | 1215 | <term><command>rescue</command></term> |
27722f96 LN |
1216 | |
1217 | <listitem> | |
e1fac8a6 ZJS |
1218 | <para>Enter rescue mode. This is equivalent to <command>systemctl isolate rescue.target</command>. This |
1219 | operation is blocking by default, use <option>--no-block</option> to request asynchronous behavior.</para> | |
27722f96 LN |
1220 | </listitem> |
1221 | </varlistentry> | |
27722f96 | 1222 | <varlistentry> |
e1fac8a6 | 1223 | <term><command>emergency</command></term> |
27722f96 LN |
1224 | |
1225 | <listitem> | |
e1fac8a6 ZJS |
1226 | <para>Enter emergency mode. This is equivalent to <command>systemctl isolate |
1227 | emergency.target</command>. This operation is blocking by default, use <option>--no-block</option> to | |
1228 | request asynchronous behavior.</para> | |
27722f96 LN |
1229 | </listitem> |
1230 | </varlistentry> | |
27722f96 | 1231 | <varlistentry> |
e1fac8a6 | 1232 | <term><command>halt</command></term> |
27722f96 LN |
1233 | |
1234 | <listitem> | |
e1fac8a6 ZJS |
1235 | <para>Shut down and halt the system. This is mostly equivalent to <command>systemctl start halt.target |
1236 | --job-mode=replace-irreversibly --no-block</command>, but also prints a wall message to all users. This command is | |
1237 | asynchronous; it will return after the halt operation is enqueued, without waiting for it to complete. Note | |
1238 | that this operation will simply halt the OS kernel after shutting down, leaving the hardware powered | |
1239 | on. Use <command>systemctl poweroff</command> for powering off the system (see below).</para> | |
1240 | ||
1241 | <para>If combined with <option>--force</option>, shutdown of all running services is skipped, however all | |
1242 | processes are killed and all file systems are unmounted or mounted read-only, immediately followed by the | |
1243 | system halt. If <option>--force</option> is specified twice, the operation is immediately executed without | |
1244 | terminating any processes or unmounting any file systems. This may result in data loss. Note that when | |
1245 | <option>--force</option> is specified twice the halt operation is executed by <command>systemctl</command> | |
1246 | itself, and the system manager is not contacted. This means the command should succeed even when the system | |
1247 | manager has crashed.</para> | |
27722f96 LN |
1248 | </listitem> |
1249 | </varlistentry> | |
27722f96 | 1250 | <varlistentry> |
e1fac8a6 | 1251 | <term><command>poweroff</command></term> |
27722f96 LN |
1252 | |
1253 | <listitem> | |
e1fac8a6 ZJS |
1254 | <para>Shut down and power-off the system. This is mostly equivalent to <command>systemctl start |
1255 | poweroff.target --job-mode=replace-irreversibly --no-block</command>, but also prints a wall message to all | |
1256 | users. This command is asynchronous; it will return after the power-off operation is enqueued, without | |
1257 | waiting for it to complete.</para> | |
27722f96 | 1258 | |
e1fac8a6 ZJS |
1259 | <para>If combined with <option>--force</option>, shutdown of all running services is skipped, however all |
1260 | processes are killed and all file systems are unmounted or mounted read-only, immediately followed by the | |
1261 | powering off. If <option>--force</option> is specified twice, the operation is immediately executed without | |
1262 | terminating any processes or unmounting any file systems. This may result in data loss. Note that when | |
1263 | <option>--force</option> is specified twice the power-off operation is executed by | |
1264 | <command>systemctl</command> itself, and the system manager is not contacted. This means the command should | |
1265 | succeed even when the system manager has crashed.</para> | |
1266 | </listitem> | |
1267 | </varlistentry> | |
1268 | <varlistentry> | |
1269 | <term><command>reboot</command> <optional><replaceable>arg</replaceable></optional></term> | |
27722f96 | 1270 | |
e1fac8a6 ZJS |
1271 | <listitem> |
1272 | <para>Shut down and reboot the system. This is mostly equivalent to <command>systemctl start reboot.target | |
1273 | --job-mode=replace-irreversibly --no-block</command>, but also prints a wall message to all users. This | |
1274 | command is asynchronous; it will return after the reboot operation is enqueued, without waiting for it to | |
1275 | complete.</para> | |
3990961d | 1276 | |
e1fac8a6 ZJS |
1277 | <para>If combined with <option>--force</option>, shutdown of all running services is skipped, however all |
1278 | processes are killed and all file systems are unmounted or mounted read-only, immediately followed by the | |
1279 | reboot. If <option>--force</option> is specified twice, the operation is immediately executed without | |
1280 | terminating any processes or unmounting any file systems. This may result in data loss. Note that when | |
1281 | <option>--force</option> is specified twice the reboot operation is executed by | |
1282 | <command>systemctl</command> itself, and the system manager is not contacted. This means the command should | |
1283 | succeed even when the system manager has crashed.</para> | |
3990961d | 1284 | |
e1fac8a6 ZJS |
1285 | <para>If the optional argument <replaceable>arg</replaceable> is given, it will be passed as the optional |
1286 | argument to the <citerefentry><refentrytitle>reboot</refentrytitle><manvolnum>2</manvolnum></citerefentry> | |
1287 | system call. The value is architecture and firmware specific. As an example, <literal>recovery</literal> | |
1288 | might be used to trigger system recovery, and <literal>fota</literal> might be used to trigger a | |
1289 | <quote>firmware over the air</quote> update.</para> | |
27722f96 LN |
1290 | </listitem> |
1291 | </varlistentry> | |
1292 | ||
1293 | <varlistentry> | |
e1fac8a6 | 1294 | <term><command>kexec</command></term> |
27722f96 LN |
1295 | |
1296 | <listitem> | |
e1fac8a6 ZJS |
1297 | <para>Shut down and reboot the system via <command>kexec</command>. This is equivalent to |
1298 | <command>systemctl start kexec.target --job-mode=replace-irreversibly --no-block</command>. This command is | |
1299 | asynchronous; it will return after the reboot operation is enqueued, without waiting for it to | |
1300 | complete.</para> | |
3990961d | 1301 | |
e1fac8a6 ZJS |
1302 | <para>If combined with <option>--force</option>, shutdown of all running services is skipped, however all |
1303 | processes are killed and all file systems are unmounted or mounted read-only, immediately followed by the | |
1304 | reboot.</para> | |
1305 | </listitem> | |
1306 | </varlistentry> | |
3990961d | 1307 | |
e1fac8a6 ZJS |
1308 | <varlistentry> |
1309 | <term><command>exit</command> <optional><replaceable>EXIT_CODE</replaceable></optional></term> | |
3990961d | 1310 | |
e1fac8a6 ZJS |
1311 | <listitem> |
1312 | <para>Ask the service manager to quit. This is only supported for user service managers (i.e. in | |
1313 | conjunction with the <option>--user</option> option) or in containers and is equivalent to | |
1314 | <command>poweroff</command> otherwise. This command is asynchronous; it will return after the exit | |
1315 | operation is enqueued, without waiting for it to complete.</para> | |
27722f96 | 1316 | |
e1fac8a6 ZJS |
1317 | <para>The service manager will exit with the specified exit code, if |
1318 | <replaceable>EXIT_CODE</replaceable> is passed.</para> | |
27722f96 LN |
1319 | </listitem> |
1320 | </varlistentry> | |
1321 | ||
b619ec8f | 1322 | <varlistentry> |
e1fac8a6 | 1323 | <term><command>switch-root</command> <replaceable>ROOT</replaceable> <optional><replaceable>INIT</replaceable></optional></term> |
b619ec8f LP |
1324 | |
1325 | <listitem> | |
e1fac8a6 ZJS |
1326 | <para>Switches to a different root directory and executes a new system manager process below it. This is |
1327 | intended for usage in initial RAM disks ("initrd"), and will transition from the initrd's system manager | |
1328 | process (a.k.a. "init" process) to the main system manager process which is loaded from the actual host | |
1329 | volume. This call takes two arguments: the directory that is to become the new root directory, and the path | |
1330 | to the new system manager binary below it to execute as PID 1. If the latter is omitted or the empty | |
1331 | string, a systemd binary will automatically be searched for and used as init. If the system manager path is | |
1332 | omitted, equal to the empty string or identical to the path to the systemd binary, the state of the | |
1333 | initrd's system manager process is passed to the main system manager, which allows later introspection of | |
1334 | the state of the services involved in the initrd boot phase.</para> | |
b619ec8f LP |
1335 | </listitem> |
1336 | </varlistentry> | |
1337 | ||
1338 | <varlistentry> | |
e1fac8a6 | 1339 | <term><command>suspend</command></term> |
b619ec8f LP |
1340 | |
1341 | <listitem> | |
e1fac8a6 ZJS |
1342 | <para>Suspend the system. This will trigger activation of the special target unit |
1343 | <filename>suspend.target</filename>. This command is asynchronous, and will return after the suspend | |
1344 | operation is successfully enqueued. It will not wait for the suspend/resume cycle to complete.</para> | |
1345 | </listitem> | |
1346 | </varlistentry> | |
39207373 | 1347 | |
e1fac8a6 ZJS |
1348 | <varlistentry> |
1349 | <term><command>hibernate</command></term> | |
b619ec8f | 1350 | |
e1fac8a6 ZJS |
1351 | <listitem> |
1352 | <para>Hibernate the system. This will trigger activation of the special target unit | |
1353 | <filename>hibernate.target</filename>. This command is asynchronous, and will return after the hibernation | |
1354 | operation is successfully enqueued. It will not wait for the hibernate/thaw cycle to complete.</para> | |
b619ec8f LP |
1355 | </listitem> |
1356 | </varlistentry> | |
1357 | ||
1358 | <varlistentry> | |
e1fac8a6 | 1359 | <term><command>hybrid-sleep</command></term> |
b619ec8f LP |
1360 | |
1361 | <listitem> | |
e1fac8a6 ZJS |
1362 | <para>Hibernate and suspend the system. This will trigger activation of the special target unit |
1363 | <filename>hybrid-sleep.target</filename>. This command is asynchronous, and will return after the hybrid | |
1364 | sleep operation is successfully enqueued. It will not wait for the sleep/wake-up cycle to complete.</para> | |
b619ec8f LP |
1365 | </listitem> |
1366 | </varlistentry> | |
1367 | ||
27722f96 | 1368 | <varlistentry> |
e1fac8a6 | 1369 | <term><command>suspend-then-hibernate</command></term> |
27722f96 LN |
1370 | |
1371 | <listitem> | |
e1fac8a6 ZJS |
1372 | <para>Suspend the system and hibernate it after the delay specified in <filename>systemd-sleep.conf</filename>. |
1373 | This will trigger activation of the special target unit <filename>suspend-then-hibernate.target</filename>. | |
1374 | This command is asynchronous, and will return after the hybrid sleep operation is successfully enqueued. | |
1375 | It will not wait for the sleep/wake-up or hibernate/thaw cycle to complete.</para> | |
1376 | </listitem> | |
1377 | </varlistentry> | |
1378 | </variablelist> | |
1379 | </refsect2> | |
171754aa | 1380 | |
e1fac8a6 ZJS |
1381 | <refsect2> |
1382 | <title>Parameter Syntax</title> | |
171754aa | 1383 | |
e1fac8a6 ZJS |
1384 | <para>Unit commands listed above take either a single unit name (designated as <replaceable>UNIT</replaceable>), |
1385 | or multiple unit specifications (designated as <replaceable>PATTERN</replaceable>…). In the first case, the | |
1386 | unit name with or without a suffix must be given. If the suffix is not specified (unit name is "abbreviated"), | |
1387 | systemctl will append a suitable suffix, <literal>.service</literal> by default, and a type-specific suffix in | |
1388 | case of commands which operate only on specific unit types. For example, | |
1389 | <programlisting># systemctl start sshd</programlisting> and | |
1390 | <programlisting># systemctl start sshd.service</programlisting> | |
1391 | are equivalent, as are | |
1392 | <programlisting># systemctl isolate default</programlisting> | |
1393 | and | |
1394 | <programlisting># systemctl isolate default.target</programlisting> | |
1395 | Note that (absolute) paths to device nodes are automatically converted to device unit names, and other (absolute) | |
1396 | paths to mount unit names. | |
1397 | <programlisting># systemctl status /dev/sda | |
1398 | # systemctl status /home</programlisting> | |
1399 | are equivalent to: | |
1400 | <programlisting># systemctl status dev-sda.device | |
1401 | # systemctl status home.mount</programlisting> | |
1402 | In the second case, shell-style globs will be matched against the primary names of all units currently in memory; | |
1403 | literal unit names, with or without a suffix, will be treated as in the first case. This means that literal unit | |
1404 | names always refer to exactly one unit, but globs may match zero units and this is not considered an | |
1405 | error.</para> | |
171754aa | 1406 | |
e1fac8a6 ZJS |
1407 | <para>Glob patterns use |
1408 | <citerefentry project='man-pages'><refentrytitle>fnmatch</refentrytitle><manvolnum>3</manvolnum></citerefentry>, | |
1409 | so normal shell-style globbing rules are used, and | |
1410 | <literal>*</literal>, <literal>?</literal>, | |
1411 | <literal>[]</literal> may be used. See | |
1412 | <citerefentry project='man-pages'><refentrytitle>glob</refentrytitle><manvolnum>7</manvolnum></citerefentry> | |
1413 | for more details. The patterns are matched against the primary names of | |
1414 | units currently in memory, and patterns which do not match anything | |
1415 | are silently skipped. For example: | |
1416 | <programlisting># systemctl stop sshd@*.service</programlisting> | |
1417 | will stop all <filename>sshd@.service</filename> instances. Note that alias names of units, and units that aren't | |
1418 | in memory are not considered for glob expansion. | |
1419 | </para> | |
27722f96 | 1420 | |
e1fac8a6 ZJS |
1421 | <para>For unit file commands, the specified <replaceable>UNIT</replaceable> should be the name of the unit file |
1422 | (possibly abbreviated, see above), or the absolute path to the unit file: | |
1423 | <programlisting># systemctl enable foo.service</programlisting> | |
1424 | or | |
1425 | <programlisting># systemctl link /path/to/foo.service</programlisting> | |
1426 | </para> | |
1427 | </refsect2> | |
27722f96 | 1428 | |
e1fac8a6 | 1429 | </refsect1> |
27722f96 | 1430 | |
e1fac8a6 ZJS |
1431 | <refsect1> |
1432 | <title>Options</title> | |
27722f96 | 1433 | |
e1fac8a6 | 1434 | <para>The following options are understood:</para> |
27722f96 | 1435 | |
e1fac8a6 ZJS |
1436 | <variablelist> |
1437 | <varlistentry> | |
1438 | <term><option>-t</option></term> | |
1439 | <term><option>--type=</option></term> | |
27722f96 | 1440 | |
e1fac8a6 ZJS |
1441 | <listitem> |
1442 | <para>The argument should be a comma-separated list of unit | |
1443 | types such as <option>service</option> and | |
1444 | <option>socket</option>. | |
1445 | </para> | |
27722f96 | 1446 | |
e1fac8a6 ZJS |
1447 | <para>If one of the arguments is a unit type, when listing |
1448 | units, limit display to certain unit types. Otherwise, units | |
1449 | of all types will be shown.</para> | |
344ca755 | 1450 | |
e1fac8a6 ZJS |
1451 | <para>As a special case, if one of the arguments is |
1452 | <option>help</option>, a list of allowed values will be | |
1453 | printed and the program will exit.</para> | |
1454 | </listitem> | |
1455 | </varlistentry> | |
344ca755 | 1456 | |
e1fac8a6 ZJS |
1457 | <varlistentry> |
1458 | <term><option>--state=</option></term> | |
344ca755 | 1459 | |
e1fac8a6 ZJS |
1460 | <listitem> |
1461 | <para>The argument should be a comma-separated list of unit | |
1462 | LOAD, SUB, or ACTIVE states. When listing units, show only | |
1463 | those in the specified states. Use <option>--state=failed</option> | |
1464 | to show only failed units.</para> | |
27722f96 | 1465 | |
e1fac8a6 ZJS |
1466 | <para>As a special case, if one of the arguments is |
1467 | <option>help</option>, a list of allowed values will be | |
1468 | printed and the program will exit.</para> | |
1469 | </listitem> | |
1470 | </varlistentry> | |
27722f96 | 1471 | |
e1fac8a6 ZJS |
1472 | <varlistentry> |
1473 | <term><option>-p</option></term> | |
1474 | <term><option>--property=</option></term> | |
27722f96 | 1475 | |
e1fac8a6 ZJS |
1476 | <listitem> |
1477 | <para>When showing unit/job/manager properties with the | |
1478 | <command>show</command> command, limit display to properties | |
1479 | specified in the argument. The argument should be a | |
1480 | comma-separated list of property names, such as | |
1481 | <literal>MainPID</literal>. Unless specified, all known | |
1482 | properties are shown. If specified more than once, all | |
1483 | properties with the specified names are shown. Shell | |
1484 | completion is implemented for property names.</para> | |
7d4fb3b1 | 1485 | |
e1fac8a6 ZJS |
1486 | <para>For the manager itself, |
1487 | <command>systemctl show</command> will show all available | |
1488 | properties. Those properties are documented in | |
1489 | <citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>. | |
1490 | </para> | |
7d4fb3b1 | 1491 | |
e1fac8a6 ZJS |
1492 | <para>Properties for units vary by unit type, so showing any |
1493 | unit (even a non-existent one) is a way to list properties | |
1494 | pertaining to this type. Similarly, showing any job will list | |
1495 | properties pertaining to all jobs. Properties for units are | |
1496 | documented in | |
1497 | <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
1498 | and the pages for individual unit types | |
1499 | <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
1500 | <citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry>, | |
1501 | etc.</para> | |
1502 | </listitem> | |
1503 | </varlistentry> | |
7d4fb3b1 | 1504 | |
e1fac8a6 ZJS |
1505 | <varlistentry> |
1506 | <term><option>-a</option></term> | |
1507 | <term><option>--all</option></term> | |
7d4fb3b1 | 1508 | |
e1fac8a6 ZJS |
1509 | <listitem> |
1510 | <para>When listing units with <command>list-units</command>, also show inactive units and | |
1511 | units which are following other units. When showing unit/job/manager properties, show all | |
1512 | properties regardless whether they are set or not.</para> | |
7d4fb3b1 | 1513 | |
e1fac8a6 ZJS |
1514 | <para>To list all units installed in the file system, use the |
1515 | <command>list-unit-files</command> command instead.</para> | |
39c38ce1 | 1516 | |
e1fac8a6 ZJS |
1517 | <para>When listing units with <command>list-dependencies</command>, recursively show |
1518 | dependencies of all dependent units (by default only dependencies of target units are | |
1519 | shown).</para> | |
7d4fb3b1 | 1520 | |
e1fac8a6 ZJS |
1521 | <para>When used with <command>status</command>, show journal messages in full, even if they include |
1522 | unprintable characters or are very long. By default, fields with unprintable characters are | |
1523 | abbreviated as "blob data". (Note that the pager may escape unprintable characters again.)</para> | |
1524 | </listitem> | |
1525 | </varlistentry> | |
7d4fb3b1 | 1526 | |
e1fac8a6 ZJS |
1527 | <varlistentry> |
1528 | <term><option>-r</option></term> | |
1529 | <term><option>--recursive</option></term> | |
7d4fb3b1 | 1530 | |
e1fac8a6 ZJS |
1531 | <listitem> |
1532 | <para>When listing units, also show units of local | |
1533 | containers. Units of local containers will be prefixed with | |
1534 | the container name, separated by a single colon character | |
1535 | (<literal>:</literal>).</para> | |
1536 | </listitem> | |
1537 | </varlistentry> | |
b619ec8f | 1538 | |
e1fac8a6 ZJS |
1539 | <varlistentry> |
1540 | <term><option>--reverse</option></term> | |
b619ec8f | 1541 | |
e1fac8a6 ZJS |
1542 | <listitem> |
1543 | <para>Show reverse dependencies between units with | |
1544 | <command>list-dependencies</command>, i.e. follow | |
1545 | dependencies of type <varname>WantedBy=</varname>, | |
1546 | <varname>RequiredBy=</varname>, | |
1547 | <varname>PartOf=</varname>, <varname>BoundBy=</varname>, | |
1548 | instead of <varname>Wants=</varname> and similar. | |
1549 | </para> | |
1550 | </listitem> | |
1551 | </varlistentry> | |
b619ec8f | 1552 | |
e1fac8a6 ZJS |
1553 | <varlistentry> |
1554 | <term><option>--after</option></term> | |
b619ec8f | 1555 | |
e1fac8a6 ZJS |
1556 | <listitem> |
1557 | <para>With <command>list-dependencies</command>, show the | |
1558 | units that are ordered before the specified unit. In other | |
1559 | words, recursively list units following the | |
1560 | <varname>After=</varname> dependency.</para> | |
b619ec8f | 1561 | |
e1fac8a6 ZJS |
1562 | <para>Note that any <varname>After=</varname> dependency is |
1563 | automatically mirrored to create a | |
1564 | <varname>Before=</varname> dependency. Temporal dependencies | |
1565 | may be specified explicitly, but are also created implicitly | |
1566 | for units which are <varname>WantedBy=</varname> targets | |
1567 | (see | |
1568 | <citerefentry><refentrytitle>systemd.target</refentrytitle><manvolnum>5</manvolnum></citerefentry>), | |
1569 | and as a result of other directives (for example | |
1570 | <varname>RequiresMountsFor=</varname>). Both explicitly | |
1571 | and implicitly introduced dependencies are shown with | |
1572 | <command>list-dependencies</command>.</para> | |
27722f96 | 1573 | |
e1fac8a6 ZJS |
1574 | <para>When passed to the <command>list-jobs</command> command, for each printed job show which other jobs are |
1575 | waiting for it. May be combined with <option>--before</option> to show both the jobs waiting for each job as | |
1576 | well as all jobs each job is waiting for.</para> | |
1577 | </listitem> | |
1578 | </varlistentry> | |
0d292f5e | 1579 | |
e1fac8a6 ZJS |
1580 | <varlistentry> |
1581 | <term><option>--before</option></term> | |
0d292f5e | 1582 | |
e1fac8a6 ZJS |
1583 | <listitem> |
1584 | <para>With <command>list-dependencies</command>, show the | |
1585 | units that are ordered after the specified unit. In other | |
1586 | words, recursively list units following the | |
1587 | <varname>Before=</varname> dependency.</para> | |
0d292f5e | 1588 | |
e1fac8a6 ZJS |
1589 | <para>When passed to the <command>list-jobs</command> command, for each printed job show which other jobs it |
1590 | is waiting for. May be combined with <option>--after</option> to show both the jobs waiting for each job as | |
1591 | well as all jobs each job is waiting for.</para> | |
1592 | </listitem> | |
1593 | </varlistentry> | |
27722f96 | 1594 | |
a602a0b4 KK |
1595 | <varlistentry> |
1596 | <term><option>--with-dependencies</option></term> | |
1597 | ||
1598 | <listitem> | |
1599 | <para>When used with <command>status</command>, | |
1600 | <command>cat</command>, <command>list-units</command>, and | |
1601 | <command>list-unit-files</command>, those commands print all | |
1602 | specified units and the dependencies of those units.</para> | |
1603 | ||
1604 | <para>Options <option>--reverse</option>, | |
1605 | <option>--after</option>, <option>--before</option> | |
1606 | may be used to change what types of dependencies | |
1607 | are shown.</para> | |
1608 | </listitem> | |
1609 | </varlistentry> | |
1610 | ||
e1fac8a6 ZJS |
1611 | <varlistentry> |
1612 | <term><option>-l</option></term> | |
1613 | <term><option>--full</option></term> | |
27722f96 | 1614 | |
e1fac8a6 ZJS |
1615 | <listitem> |
1616 | <para>Do not ellipsize unit names, process tree entries, | |
1617 | journal output, or truncate unit descriptions in the output | |
1618 | of <command>status</command>, <command>list-units</command>, | |
1619 | <command>list-jobs</command>, and | |
1620 | <command>list-timers</command>.</para> | |
1621 | <para>Also, show installation targets in the output of | |
1622 | <command>is-enabled</command>.</para> | |
1623 | </listitem> | |
1624 | </varlistentry> | |
82948f6c | 1625 | |
e1fac8a6 ZJS |
1626 | <varlistentry> |
1627 | <term><option>--value</option></term> | |
27722f96 | 1628 | |
e1fac8a6 ZJS |
1629 | <listitem> |
1630 | <para>When printing properties with <command>show</command>, | |
1631 | only print the value, and skip the property name and | |
1632 | <literal>=</literal>.</para> | |
1633 | </listitem> | |
1634 | </varlistentry> | |
27722f96 | 1635 | |
e1fac8a6 ZJS |
1636 | <varlistentry> |
1637 | <term><option>--show-types</option></term> | |
27722f96 | 1638 | |
e1fac8a6 ZJS |
1639 | <listitem> |
1640 | <para>When showing sockets, show the type of the socket.</para> | |
1641 | </listitem> | |
1642 | </varlistentry> | |
27722f96 | 1643 | |
e1fac8a6 ZJS |
1644 | <varlistentry> |
1645 | <term><option>--job-mode=</option></term> | |
27722f96 | 1646 | |
e1fac8a6 ZJS |
1647 | <listitem> |
1648 | <para>When queuing a new job, this option controls how to deal with | |
1649 | already queued jobs. It takes one of <literal>fail</literal>, | |
1650 | <literal>replace</literal>, | |
1651 | <literal>replace-irreversibly</literal>, | |
1652 | <literal>isolate</literal>, | |
1653 | <literal>ignore-dependencies</literal>, | |
132e0b53 KK |
1654 | <literal>ignore-requirements</literal>, |
1655 | <literal>flush</literal>, or | |
1656 | <literal>triggering</literal>. Defaults to | |
e1fac8a6 ZJS |
1657 | <literal>replace</literal>, except when the |
1658 | <command>isolate</command> command is used which implies the | |
1659 | <literal>isolate</literal> job mode.</para> | |
27722f96 | 1660 | |
e1fac8a6 ZJS |
1661 | <para>If <literal>fail</literal> is specified and a requested |
1662 | operation conflicts with a pending job (more specifically: | |
1663 | causes an already pending start job to be reversed into a stop | |
1664 | job or vice versa), cause the operation to fail.</para> | |
ac3efa8a | 1665 | |
e1fac8a6 ZJS |
1666 | <para>If <literal>replace</literal> (the default) is |
1667 | specified, any conflicting pending job will be replaced, as | |
1668 | necessary.</para> | |
27722f96 | 1669 | |
e1fac8a6 ZJS |
1670 | <para>If <literal>replace-irreversibly</literal> is specified, |
1671 | operate like <literal>replace</literal>, but also mark the new | |
1672 | jobs as irreversible. This prevents future conflicting | |
1673 | transactions from replacing these jobs (or even being enqueued | |
1674 | while the irreversible jobs are still pending). Irreversible | |
1675 | jobs can still be cancelled using the <command>cancel</command> | |
1676 | command. This job mode should be used on any transaction which | |
1677 | pulls in <filename>shutdown.target</filename>.</para> | |
27722f96 | 1678 | |
e1fac8a6 ZJS |
1679 | <para><literal>isolate</literal> is only valid for start |
1680 | operations and causes all other units to be stopped when the | |
1681 | specified unit is started. This mode is always used when the | |
1682 | <command>isolate</command> command is used.</para> | |
27722f96 | 1683 | |
e1fac8a6 ZJS |
1684 | <para><literal>flush</literal> will cause all queued jobs to |
1685 | be canceled when the new job is enqueued.</para> | |
432d5965 | 1686 | |
e1fac8a6 ZJS |
1687 | <para>If <literal>ignore-dependencies</literal> is specified, |
1688 | then all unit dependencies are ignored for this new job and | |
1689 | the operation is executed immediately. If passed, no required | |
1690 | units of the unit passed will be pulled in, and no ordering | |
1691 | dependencies will be honored. This is mostly a debugging and | |
1692 | rescue tool for the administrator and should not be used by | |
1693 | applications.</para> | |
27722f96 | 1694 | |
e1fac8a6 ZJS |
1695 | <para><literal>ignore-requirements</literal> is similar to |
1696 | <literal>ignore-dependencies</literal>, but only causes the | |
1697 | requirement dependencies to be ignored, the ordering | |
1698 | dependencies will still be honored.</para> | |
1699 | </listitem> | |
27722f96 | 1700 | |
132e0b53 KK |
1701 | <para><literal>triggering</literal> may only be used with |
1702 | <command>systemctl stop</command>. In this mode, the specified | |
1703 | unit and any active units that trigger it are stopped. See the | |
1704 | discussion of | |
1705 | <varname>Triggers=</varname> in <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry> | |
1706 | for more information about triggering units.</para> | |
1707 | ||
e1fac8a6 | 1708 | </varlistentry> |
27722f96 | 1709 | |
e1fac8a6 ZJS |
1710 | <varlistentry> |
1711 | <term><option>-T</option></term> | |
1712 | <term><option>--show-transaction</option></term> | |
99813a19 | 1713 | |
e1fac8a6 ZJS |
1714 | <listitem> |
1715 | <para>When enqueuing a unit job (for example as effect of a <command>systemctl start</command> | |
1716 | invocation or similar), show brief information about all jobs enqueued, covering both the requested | |
1717 | job and any added because of unit dependencies. Note that the output will only include jobs | |
1718 | immediately part of the transaction requested. It is possible that service start-up program code | |
1719 | run as effect of the enqueued jobs might request further jobs to be pulled in. This means that | |
1720 | completion of the listed jobs might ultimately entail more jobs than the listed ones.</para> | |
1721 | </listitem> | |
1722 | </varlistentry> | |
2de51fdc | 1723 | |
e1fac8a6 ZJS |
1724 | <varlistentry> |
1725 | <term><option>--fail</option></term> | |
adb6cd9b | 1726 | |
e1fac8a6 ZJS |
1727 | <listitem> |
1728 | <para>Shorthand for <option>--job-mode=</option>fail.</para> | |
1729 | <para>When used with the <command>kill</command> command, | |
1730 | if no units were killed, the operation results in an error. | |
1731 | </para> | |
1732 | </listitem> | |
1733 | </varlistentry> | |
99813a19 | 1734 | |
e1fac8a6 ZJS |
1735 | <varlistentry> |
1736 | <term><option>-i</option></term> | |
1737 | <term><option>--ignore-inhibitors</option></term> | |
27722f96 | 1738 | |
e1fac8a6 ZJS |
1739 | <listitem> |
1740 | <para>When system shutdown or a sleep state is requested, ignore inhibitor locks. Applications can establish | |
1741 | inhibitor locks to avoid that certain important operations (such as CD burning or suchlike) are interrupted | |
1742 | by system shutdown or a sleep state. Any user may take these locks and privileged users may override these | |
1743 | locks. If any locks are taken, shutdown and sleep state requests will normally fail (unless privileged) and a | |
1744 | list of active locks is printed. However, if <option>--ignore-inhibitors</option> is specified, the | |
1745 | established locks are ignored and not shown, and the operation attempted anyway, possibly requiring | |
1746 | additional privileges.</para> | |
1747 | </listitem> | |
1748 | </varlistentry> | |
99813a19 | 1749 | |
e1fac8a6 ZJS |
1750 | <varlistentry> |
1751 | <term><option>--dry-run</option></term> | |
27722f96 | 1752 | |
e1fac8a6 ZJS |
1753 | <listitem> |
1754 | <para>Just print what would be done. Currently supported by verbs | |
1755 | <command>halt</command>, <command>poweroff</command>, <command>reboot</command>, | |
1756 | <command>kexec</command>, <command>suspend</command>, <command>hibernate</command>, | |
1757 | <command>hybrid-sleep</command>, <command>suspend-then-hibernate</command>, | |
1758 | <command>default</command>, <command>rescue</command>, | |
1759 | <command>emergency</command>, and <command>exit</command>.</para> | |
1760 | </listitem> | |
1761 | </varlistentry> | |
27722f96 | 1762 | |
e1fac8a6 ZJS |
1763 | <varlistentry> |
1764 | <term><option>-q</option></term> | |
1765 | <term><option>--quiet</option></term> | |
27722f96 | 1766 | |
e1fac8a6 ZJS |
1767 | <listitem> |
1768 | <para>Suppress printing of the results of various commands | |
1769 | and also the hints about truncated log lines. This does not | |
1770 | suppress output of commands for which the printed output is | |
1771 | the only result (like <command>show</command>). Errors are | |
1772 | always printed.</para> | |
1773 | </listitem> | |
1774 | </varlistentry> | |
6324a8a7 | 1775 | |
e1fac8a6 ZJS |
1776 | <varlistentry> |
1777 | <term><option>--no-block</option></term> | |
27722f96 | 1778 | |
e1fac8a6 ZJS |
1779 | <listitem> |
1780 | <para>Do not synchronously wait for the requested operation | |
1781 | to finish. If this is not specified, the job will be | |
1782 | verified, enqueued and <command>systemctl</command> will | |
1783 | wait until the unit's start-up is completed. By passing this | |
1784 | argument, it is only verified and enqueued. This option may not be | |
1785 | combined with <option>--wait</option>.</para> | |
1786 | </listitem> | |
1787 | </varlistentry> | |
6324a8a7 | 1788 | |
e1fac8a6 ZJS |
1789 | <varlistentry> |
1790 | <term><option>--wait</option></term> | |
1791 | ||
1792 | <listitem> | |
1793 | <para>Synchronously wait for started units to terminate again. | |
1794 | This option may not be combined with <option>--no-block</option>. | |
1795 | Note that this will wait forever if any given unit never terminates | |
1796 | (by itself or by getting stopped explicitly); particularly services | |
1797 | which use <literal>RemainAfterExit=yes</literal>.</para> | |
1798 | ||
1799 | <para>When used with <command>is-system-running</command>, wait | |
1800 | until the boot process is completed before returning.</para> | |
1801 | </listitem> | |
1802 | </varlistentry> | |
1803 | ||
1804 | <xi:include href="user-system-options.xml" xpointer="user" /> | |
1805 | <xi:include href="user-system-options.xml" xpointer="system" /> | |
1806 | ||
1807 | <varlistentry> | |
1808 | <term><option>--failed</option></term> | |
1809 | ||
1810 | <listitem> | |
1811 | <para>List units in failed state. This is equivalent to | |
1812 | <option>--state=failed</option>.</para> | |
1813 | </listitem> | |
1814 | </varlistentry> | |
1815 | ||
1816 | <varlistentry> | |
1817 | <term><option>--no-wall</option></term> | |
1818 | ||
1819 | <listitem> | |
1820 | <para>Do not send wall message before halt, power-off and reboot.</para> | |
1821 | </listitem> | |
1822 | </varlistentry> | |
1823 | ||
1824 | <varlistentry> | |
1825 | <term><option>--global</option></term> | |
1826 | ||
1827 | <listitem> | |
1828 | <para>When used with <command>enable</command> and | |
1829 | <command>disable</command>, operate on the global user | |
1830 | configuration directory, thus enabling or disabling a unit | |
1831 | file globally for all future logins of all users.</para> | |
1832 | </listitem> | |
1833 | </varlistentry> | |
1834 | ||
1835 | <varlistentry> | |
1836 | <term><option>--no-reload</option></term> | |
1837 | ||
1838 | <listitem> | |
1839 | <para>When used with <command>enable</command> and | |
1840 | <command>disable</command>, do not implicitly reload daemon | |
1841 | configuration after executing the changes.</para> | |
1842 | </listitem> | |
1843 | </varlistentry> | |
1844 | ||
1845 | <varlistentry> | |
1846 | <term><option>--no-ask-password</option></term> | |
1847 | ||
1848 | <listitem> | |
1849 | <para>When used with <command>start</command> and related | |
1850 | commands, disables asking for passwords. Background services | |
1851 | may require input of a password or passphrase string, for | |
1852 | example to unlock system hard disks or cryptographic | |
1853 | certificates. Unless this option is specified and the | |
1854 | command is invoked from a terminal, | |
1855 | <command>systemctl</command> will query the user on the | |
1856 | terminal for the necessary secrets. Use this option to | |
1857 | switch this behavior off. In this case, the password must be | |
1858 | supplied by some other means (for example graphical password | |
1859 | agents) or the service might fail. This also disables | |
1860 | querying the user for authentication for privileged | |
1861 | operations.</para> | |
1862 | </listitem> | |
1863 | </varlistentry> | |
1864 | ||
1865 | <varlistentry> | |
1866 | <term><option>--kill-who=</option></term> | |
1867 | ||
1868 | <listitem> | |
1869 | <para>When used with <command>kill</command>, choose which | |
1870 | processes to send a signal to. Must be one of | |
1871 | <option>main</option>, <option>control</option> or | |
1872 | <option>all</option> to select whether to kill only the main | |
1873 | process, the control process or all processes of the | |
1874 | unit. The main process of the unit is the one that defines | |
1875 | the life-time of it. A control process of a unit is one that | |
1876 | is invoked by the manager to induce state changes of it. For | |
1877 | example, all processes started due to the | |
1878 | <varname>ExecStartPre=</varname>, | |
1879 | <varname>ExecStop=</varname> or | |
1880 | <varname>ExecReload=</varname> settings of service units are | |
1881 | control processes. Note that there is only one control | |
1882 | process per unit at a time, as only one state change is | |
1883 | executed at a time. For services of type | |
1884 | <varname>Type=forking</varname>, the initial process started | |
1885 | by the manager for <varname>ExecStart=</varname> is a | |
1886 | control process, while the process ultimately forked off by | |
1887 | that one is then considered the main process of the unit (if | |
1888 | it can be determined). This is different for service units | |
1889 | of other types, where the process forked off by the manager | |
1890 | for <varname>ExecStart=</varname> is always the main process | |
1891 | itself. A service unit consists of zero or one main process, | |
1892 | zero or one control process plus any number of additional | |
1893 | processes. Not all unit types manage processes of these | |
1894 | types however. For example, for mount units, control processes | |
1895 | are defined (which are the invocations of | |
1896 | <filename>&MOUNT_PATH;</filename> and | |
1897 | <filename>&UMOUNT_PATH;</filename>), but no main process | |
1898 | is defined. If omitted, defaults to | |
1899 | <option>all</option>.</para> | |
1900 | </listitem> | |
1901 | ||
1902 | </varlistentry> | |
1903 | ||
1904 | <varlistentry> | |
1905 | <term><option>-s</option></term> | |
1906 | <term><option>--signal=</option></term> | |
1907 | ||
1908 | <listitem> | |
1909 | <para>When used with <command>kill</command>, choose which | |
1910 | signal to send to selected processes. Must be one of the | |
1911 | well-known signal specifiers such as <constant>SIGTERM</constant>, <constant>SIGINT</constant> or | |
1912 | <constant>SIGSTOP</constant>. If omitted, defaults to | |
1913 | <option>SIGTERM</option>.</para> | |
1914 | </listitem> | |
1915 | </varlistentry> | |
1916 | ||
1917 | <varlistentry> | |
1918 | <term><option>--what=</option></term> | |
1919 | ||
1920 | <listitem> | |
1921 | <para>Select what type of per-unit resources to remove when the <command>clean</command> command is | |
1922 | invoked, see below. Takes one of <constant>configuration</constant>, <constant>state</constant>, | |
1923 | <constant>cache</constant>, <constant>logs</constant>, <constant>runtime</constant> to select the | |
1924 | type of resource. This option may be specified more than once, in which case all specified resource | |
1925 | types are removed. Also accepts the special value <constant>all</constant> as a shortcut for | |
11fcfc53 | 1926 | specifying all five resource types. If this option is not specified defaults to the combination of |
e1fac8a6 ZJS |
1927 | <constant>cache</constant> and <constant>runtime</constant>, i.e. the two kinds of resources that |
1928 | are generally considered to be redundant and can be reconstructed on next invocation.</para> | |
1929 | </listitem> | |
1930 | </varlistentry> | |
1931 | ||
1932 | <varlistentry> | |
1933 | <term><option>-f</option></term> | |
1934 | <term><option>--force</option></term> | |
1935 | ||
1936 | <listitem> | |
1937 | <para>When used with <command>enable</command>, overwrite | |
1938 | any existing conflicting symlinks.</para> | |
1939 | ||
1940 | <para>When used with <command>edit</command>, create all of the | |
1941 | specified units which do not already exist.</para> | |
1942 | ||
1943 | <para>When used with <command>halt</command>, <command>poweroff</command>, <command>reboot</command> or | |
1944 | <command>kexec</command>, execute the selected operation without shutting down all units. However, all | |
1945 | processes will be killed forcibly and all file systems are unmounted or remounted read-only. This is hence a | |
1946 | drastic but relatively safe option to request an immediate reboot. If <option>--force</option> is specified | |
1947 | twice for these operations (with the exception of <command>kexec</command>), they will be executed | |
1948 | immediately, without terminating any processes or unmounting any file systems. Warning: specifying | |
1949 | <option>--force</option> twice with any of these operations might result in data loss. Note that when | |
1950 | <option>--force</option> is specified twice the selected operation is executed by | |
1951 | <command>systemctl</command> itself, and the system manager is not contacted. This means the command should | |
1952 | succeed even when the system manager has crashed.</para> | |
1953 | </listitem> | |
1954 | </varlistentry> | |
27722f96 | 1955 | |
e1fac8a6 ZJS |
1956 | <varlistentry> |
1957 | <term><option>--message=</option></term> | |
6324a8a7 | 1958 | |
e1fac8a6 ZJS |
1959 | <listitem> |
1960 | <para>When used with <command>halt</command>, <command>poweroff</command> or <command>reboot</command>, set a | |
1961 | short message explaining the reason for the operation. The message will be logged together with the default | |
1962 | shutdown message.</para> | |
1963 | </listitem> | |
1964 | </varlistentry> | |
6324a8a7 | 1965 | |
e1fac8a6 ZJS |
1966 | <varlistentry> |
1967 | <term><option>--now</option></term> | |
b619ec8f | 1968 | |
e1fac8a6 ZJS |
1969 | <listitem> |
1970 | <para>When used with <command>enable</command>, the units | |
1971 | will also be started. When used with <command>disable</command> or | |
1972 | <command>mask</command>, the units will also be stopped. The start | |
1973 | or stop operation is only carried out when the respective enable or | |
1974 | disable operation has been successful.</para> | |
1975 | </listitem> | |
1976 | </varlistentry> | |
27722f96 | 1977 | |
e1fac8a6 ZJS |
1978 | <varlistentry> |
1979 | <term><option>--root=</option></term> | |
6324a8a7 | 1980 | |
e1fac8a6 ZJS |
1981 | <listitem> |
1982 | <para>When used with | |
1983 | <command>enable</command>/<command>disable</command>/<command>is-enabled</command> | |
1984 | (and related commands), use the specified root path when looking for unit | |
1985 | files. If this option is present, <command>systemctl</command> will operate on | |
1986 | the file system directly, instead of communicating with the <command>systemd</command> | |
1987 | daemon to carry out changes.</para> | |
1988 | </listitem> | |
b619ec8f | 1989 | |
e1fac8a6 | 1990 | </varlistentry> |
27722f96 | 1991 | |
e1fac8a6 ZJS |
1992 | <varlistentry> |
1993 | <term><option>--runtime</option></term> | |
6324a8a7 | 1994 | |
e1fac8a6 ZJS |
1995 | <listitem> |
1996 | <para>When used with <command>enable</command>, | |
1997 | <command>disable</command>, <command>edit</command>, | |
1998 | (and related commands), make changes only temporarily, so | |
1999 | that they are lost on the next reboot. This will have the | |
2000 | effect that changes are not made in subdirectories of | |
2001 | <filename>/etc</filename> but in <filename>/run</filename>, | |
2002 | with identical immediate effects, however, since the latter | |
2003 | is lost on reboot, the changes are lost too.</para> | |
27722f96 | 2004 | |
e1fac8a6 ZJS |
2005 | <para>Similarly, when used with |
2006 | <command>set-property</command>, make changes only | |
2007 | temporarily, so that they are lost on the next | |
2008 | reboot.</para> | |
2009 | </listitem> | |
2010 | </varlistentry> | |
b619ec8f | 2011 | |
e1fac8a6 ZJS |
2012 | <varlistentry> |
2013 | <term><option>--preset-mode=</option></term> | |
b619ec8f | 2014 | |
e1fac8a6 ZJS |
2015 | <listitem> |
2016 | <para>Takes one of <literal>full</literal> (the default), | |
2017 | <literal>enable-only</literal>, | |
2018 | <literal>disable-only</literal>. When used with the | |
2019 | <command>preset</command> or <command>preset-all</command> | |
2020 | commands, controls whether units shall be disabled and | |
2021 | enabled according to the preset rules, or only enabled, or | |
2022 | only disabled.</para> | |
2023 | </listitem> | |
2024 | </varlistentry> | |
27722f96 | 2025 | |
e1fac8a6 ZJS |
2026 | <varlistentry> |
2027 | <term><option>-n</option></term> | |
2028 | <term><option>--lines=</option></term> | |
b619ec8f | 2029 | |
e1fac8a6 ZJS |
2030 | <listitem> |
2031 | <para>When used with <command>status</command>, controls the number of journal lines to show, counting from | |
2032 | the most recent ones. Takes a positive integer argument, or 0 to disable journal output. Defaults to | |
2033 | 10.</para> | |
2034 | </listitem> | |
2035 | </varlistentry> | |
27722f96 | 2036 | |
e1fac8a6 ZJS |
2037 | <varlistentry> |
2038 | <term><option>-o</option></term> | |
2039 | <term><option>--output=</option></term> | |
b619ec8f | 2040 | |
e1fac8a6 ZJS |
2041 | <listitem> |
2042 | <para>When used with <command>status</command>, controls the | |
2043 | formatting of the journal entries that are shown. For the | |
2044 | available choices, see | |
2045 | <citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>. | |
2046 | Defaults to <literal>short</literal>.</para> | |
2047 | </listitem> | |
2048 | </varlistentry> | |
27722f96 | 2049 | |
e1fac8a6 ZJS |
2050 | <varlistentry> |
2051 | <term><option>--firmware-setup</option></term> | |
6cc2b882 | 2052 | |
e1fac8a6 ZJS |
2053 | <listitem> |
2054 | <para>When used with the <command>reboot</command> command, indicate to the system's firmware to reboot into | |
2055 | the firmware setup interface. Note that this functionality is not available on all systems.</para> | |
2056 | </listitem> | |
2057 | </varlistentry> | |
6cc2b882 | 2058 | |
e1fac8a6 ZJS |
2059 | <varlistentry> |
2060 | <term><option>--boot-loader-menu=</option></term> | |
4a6022f0 | 2061 | |
e1fac8a6 ZJS |
2062 | <listitem> |
2063 | <para>When used with the <command>reboot</command> command, indicate to the system's boot loader to show the | |
2064 | boot loader menu on the following boot. Takes a time value as parameter — indicating the menu time-out. Pass | |
2065 | zero in order to disable the menu time-out. Note that not all boot loaders support this | |
2066 | functionality.</para> | |
2067 | </listitem> | |
2068 | </varlistentry> | |
a7c0e5d7 | 2069 | |
e1fac8a6 ZJS |
2070 | <varlistentry> |
2071 | <term><option>--boot-loader-entry=</option></term> | |
e3e0314b | 2072 | |
e1fac8a6 ZJS |
2073 | <listitem> |
2074 | <para>When used with the <command>reboot</command> command, indicate to the system's boot loader to boot into | |
2075 | a specific boot loader entry on the following boot. Takes a boot loader entry identifier as argument, or | |
2076 | <literal>help</literal> in order to list available entries. Note that not all boot loaders support this | |
2077 | functionality.</para> | |
2078 | </listitem> | |
2079 | </varlistentry> | |
e3e0314b | 2080 | |
e1fac8a6 ZJS |
2081 | <varlistentry> |
2082 | <term><option>--plain</option></term> | |
a7c0e5d7 | 2083 | |
e1fac8a6 ZJS |
2084 | <listitem> |
2085 | <para>When used with <command>list-dependencies</command>, | |
2086 | <command>list-units</command> or <command>list-machines</command>, | |
2087 | the output is printed as a list instead of a tree, and the bullet | |
2088 | circles are omitted.</para> | |
2089 | </listitem> | |
2090 | </varlistentry> | |
2091 | ||
2092 | <xi:include href="user-system-options.xml" xpointer="host" /> | |
2093 | <xi:include href="user-system-options.xml" xpointer="machine" /> | |
2094 | ||
2095 | <xi:include href="standard-options.xml" xpointer="no-pager" /> | |
2096 | <xi:include href="standard-options.xml" xpointer="no-legend" /> | |
2097 | <xi:include href="standard-options.xml" xpointer="help" /> | |
2098 | <xi:include href="standard-options.xml" xpointer="version" /> | |
2099 | </variablelist> | |
4a6022f0 ZJS |
2100 | </refsect1> |
2101 | ||
2102 | <refsect1> | |
2103 | <title>Exit status</title> | |
2104 | ||
23a9ffb0 ZJS |
2105 | <para>On success, 0 is returned, a non-zero failure code otherwise.</para> |
2106 | ||
2107 | <para><command>systemctl</command> uses the return codes defined by LSB, as defined in | |
2108 | <ulink url="http://refspecs.linuxbase.org/LSB_3.0.0/LSB-PDA/LSB-PDA/iniscrptact.html">LSB 3.0.0</ulink>. | |
2109 | </para> | |
2110 | ||
2111 | <table> | |
2112 | <title>LSB return codes</title> | |
2113 | ||
2114 | <tgroup cols='3'> | |
2115 | <thead> | |
2116 | <row> | |
2117 | <entry>Value</entry> | |
2118 | <entry>Description in LSB</entry> | |
2119 | <entry>Use in systemd</entry> | |
2120 | </row> | |
2121 | </thead> | |
2122 | <tbody> | |
2123 | <row> | |
2124 | <entry><constant>0</constant></entry> | |
2125 | <entry>"program is running or service is OK"</entry> | |
2126 | <entry>unit is active</entry> | |
2127 | </row> | |
2128 | <row> | |
2129 | <entry><constant>1</constant></entry> | |
2130 | <entry>"program is dead and <filename>/var/run</filename> pid file exists"</entry> | |
2131 | <entry>unit <emphasis>not</emphasis> failed (used by <command>is-failed</command>)</entry> | |
2132 | </row> | |
2133 | <row> | |
2134 | <entry><constant>2</constant></entry> | |
2135 | <entry>"program is dead and <filename>/var/lock</filename> lock file exists"</entry> | |
2136 | <entry>unused</entry> | |
2137 | </row> | |
2138 | <row> | |
2139 | <entry><constant>3</constant></entry> | |
2140 | <entry>"program is not running"</entry> | |
2141 | <entry>unit is not active</entry> | |
2142 | </row> | |
2143 | <row> | |
2144 | <entry><constant>4</constant></entry> | |
2145 | <entry>"program or service status is unknown"</entry> | |
2146 | <entry>no such unit</entry> | |
2147 | </row> | |
2148 | </tbody> | |
2149 | </tgroup> | |
2150 | </table> | |
2151 | ||
2152 | <para>The mapping of LSB service states to systemd unit states is imperfect, so it is better to | |
2153 | not rely on those return values but to look for specific unit states and substates instead. | |
2154 | </para> | |
4a6022f0 ZJS |
2155 | </refsect1> |
2156 | ||
7d4fb3b1 RC |
2157 | <refsect1> |
2158 | <title>Environment</title> | |
2159 | ||
2160 | <variablelist class='environment-variables'> | |
2161 | <varlistentry> | |
2162 | <term><varname>$SYSTEMD_EDITOR</varname></term> | |
2163 | ||
2164 | <listitem><para>Editor to use when editing units; overrides | |
2165 | <varname>$EDITOR</varname> and <varname>$VISUAL</varname>. If neither | |
2166 | <varname>$SYSTEMD_EDITOR</varname> nor <varname>$EDITOR</varname> nor | |
2167 | <varname>$VISUAL</varname> are present or if it is set to an empty | |
2168 | string or if their execution failed, systemctl will try to execute well | |
2169 | known editors in this order: | |
9391a1c3 | 2170 | <citerefentry project='die-net'><refentrytitle>editor</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |
3ba3a79d ZJS |
2171 | <citerefentry project='die-net'><refentrytitle>nano</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |
2172 | <citerefentry project='die-net'><refentrytitle>vim</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
2173 | <citerefentry project='die-net'><refentrytitle>vi</refentrytitle><manvolnum>1</manvolnum></citerefentry>. | |
7d4fb3b1 RC |
2174 | </para></listitem> |
2175 | </varlistentry> | |
2176 | </variablelist> | |
2177 | <xi:include href="less-variables.xml" xpointer="pager"/> | |
2178 | <xi:include href="less-variables.xml" xpointer="less"/> | |
6e16066e | 2179 | <xi:include href="less-variables.xml" xpointer="lesscharset"/> |
3d58bfc0 ZJS |
2180 | <xi:include href="less-variables.xml" xpointer="colors"/> |
2181 | <xi:include href="less-variables.xml" xpointer="urlify"/> | |
7d4fb3b1 | 2182 | </refsect1> |
4a6022f0 ZJS |
2183 | |
2184 | <refsect1> | |
2185 | <title>See Also</title> | |
2186 | <para> | |
2187 | <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
4a6022f0 ZJS |
2188 | <citerefentry><refentrytitle>journalctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |
2189 | <citerefentry><refentrytitle>loginctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>, | |
a03fe1a5 | 2190 | <citerefentry><refentrytitle>machinectl</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |
4a6022f0 | 2191 | <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>, |
ee41f602 | 2192 | <citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>, |
4a6022f0 | 2193 | <citerefentry><refentrytitle>systemd.special</refentrytitle><manvolnum>7</manvolnum></citerefentry>, |
5aded369 | 2194 | <citerefentry project='man-pages'><refentrytitle>wall</refentrytitle><manvolnum>1</manvolnum></citerefentry>, |
7d4fb3b1 | 2195 | <citerefentry><refentrytitle>systemd.preset</refentrytitle><manvolnum>5</manvolnum></citerefentry>, |
432d5965 | 2196 | <citerefentry><refentrytitle>systemd.generator</refentrytitle><manvolnum>7</manvolnum></citerefentry>, |
decde8cd | 2197 | <citerefentry project='man-pages'><refentrytitle>glob</refentrytitle><manvolnum>7</manvolnum></citerefentry> |
4a6022f0 ZJS |
2198 | </para> |
2199 | </refsect1> | |
7874bcd6 LP |
2200 | |
2201 | </refentry> |