1
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>systemd.special</title><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" title="systemd.special"><a name="systemd.special"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>systemd.special — special systemd units</p></div><div class="refsynopsisdiv" title="Synopsis"><h2>Synopsis</h2><p><code class="filename">basic.target</code>,
2
<code class="filename">ctrl-alt-del.target</code>,
3
<code class="filename">dbus.service</code>,
4
<code class="filename">default.target</code>,
5
<code class="filename">display-manager.service</code>,
6
<code class="filename">emergency.target</code>,
7
<code class="filename">exit.service</code>,
8
<code class="filename">graphical.target</code>,
9
<code class="filename">halt.target</code>,
10
<code class="filename">kbrequest.target</code>,
11
<code class="filename">local-fs.target</code>,
12
<code class="filename">local-fs-pre.target</code>,
13
<code class="filename">mail-transfer-agent.target</code>,
14
<code class="filename">multi-user.target</code>,
15
<code class="filename">network.target</code>,
16
<code class="filename">nss-lookup.target</code>,
17
<code class="filename">poweroff.target</code>,
18
<code class="filename">reboot.target</code>,
19
<code class="filename">remote-fs.target</code>,
20
<code class="filename">remote-fs-pre.target</code>,
21
<code class="filename">rescue.target</code>,
22
<code class="filename">rpcbind.target</code>,
23
<code class="filename">runlevel2.target</code>,
24
<code class="filename">runlevel3.target</code>,
25
<code class="filename">runlevel4.target</code>,
26
<code class="filename">runlevel5.target</code>,
27
<code class="filename">shutdown.target</code>,
28
<code class="filename">sigpwr.target</code>,
29
<code class="filename">sockets.target</code>,
30
<code class="filename">swap.target</code>,
31
<code class="filename">sysinit.target</code>,
32
<code class="filename">syslog.target</code>,
33
<code class="filename">systemd-initctl.service</code>,
34
<code class="filename">systemd-initctl.socket</code>,
35
<code class="filename">systemd-stdout-syslog-bridge.service</code>,
36
<code class="filename">systemd-stdout-syslog-bridge.socket</code>,
37
<code class="filename">time-sync.target</code>,
38
<code class="filename">umount.target</code></p></div><div class="refsect1" title="Description"><a name="id548796"></a><h2>Description</h2><p>A few units are treated specially by
39
systemd. They have special internal semantics and
40
cannot be renamed.</p></div><div class="refsect1" title="Special System Units"><a name="id548807"></a><h2>Special System Units</h2><div class="variablelist"><dl><dt><span class="term"><code class="filename">basic.target</code></span></dt><dd><p>A special target unit
41
covering early boot-up.</p><p>systemd automatically
42
adds dependencies of the types
43
Requires and After for this
44
target unit to all SysV
45
service units configured for
46
runlevel 1 to 5.</p><p>Usually this should pull-in
47
all sockets, mount points,
48
swap devices and other basic
49
initialization necessary for
51
daemons. Most normal daemons
52
should have dependencies of
53
type After and Requires on
54
this unit.</p></dd><dt><span class="term"><code class="filename">ctrl-alt-del.target</code></span></dt><dd><p>systemd starts this
56
Control+Alt+Del is pressed on
57
the console. Usually this
58
should be aliased (symlinked)
60
<code class="filename">reboot.target</code>.</p></dd><dt><span class="term"><code class="filename">dbus.service</code></span></dt><dd><p>A special unit for the
61
D-Bus system bus. As soon as
62
this service is fully started
63
up systemd will connect to it
65
service.</p></dd><dt><span class="term"><code class="filename">default.target</code></span></dt><dd><p>The default unit systemd
66
starts at bootup. Usually this
67
should be aliased (symlinked)
69
<code class="filename">multi-user.target</code>
71
<code class="filename">graphical.target</code>.</p><p>The default unit systemd
72
starts at bootup can be
74
<code class="varname">systemd.unit=</code>
75
kernel command line option.</p></dd><dt><span class="term"><code class="filename">display-manager.service</code></span></dt><dd><p>The display manager
76
service. Usually this should
77
be aliased (symlinked) to
78
<code class="filename">xdm.service</code>
79
or a similar display manager
80
service.</p><p>systemd automatically
81
adds dependencies of type
82
After for this target unit to
83
all SysV init script service
84
units with a LSB header
86
<code class="literal">$x-display-manager</code>
87
facility, for compatibility
88
with Debian.</p></dd><dt><span class="term"><code class="filename">emergency.target</code></span></dt><dd><p>A special target unit
89
that starts an emergency
91
console. This unit is supposed
92
to be used with the kernel
94
<code class="varname">systemd.unit=</code>
95
and has otherwise little use.
96
</p></dd><dt><span class="term"><code class="filename">graphical.target</code></span></dt><dd><p>A special target unit
97
for setting up a graphical
98
login screen. This pulls in
99
<code class="filename">multi-user.target</code>.</p><p>Units that are needed
100
for graphical login shall add
101
Wants dependencies for their
102
unit to this unit (or
103
<code class="filename">multi-user.target</code>)
104
during installation.</p></dd><dt><span class="term"><code class="filename">halt.target</code></span></dt><dd><p>A special target unit
105
for shutting down and halting the system.</p><p>Applications wanting to
106
halt the system should start
107
this unit.</p></dd><dt><span class="term"><code class="filename">kbrequest.target</code></span></dt><dd><p>systemd starts this
108
target whenever Alt+ArrowUp is
109
pressed on the console. This
110
is a good candidate to be
111
aliased (symlinked) to
112
<code class="filename">rescue.target</code>.</p></dd><dt><span class="term"><code class="filename">local-fs.target</code></span></dt><dd><p>systemd automatically
113
adds dependencies of type
114
After to all mount units that
115
refer to local mount points
116
for this target unit. In
117
addition, systemd adds
118
dependencies of type Wants to
119
this target unit for those
121
<code class="filename">/etc/fstab</code>
123
<code class="option">auto</code> and
124
<code class="option">comment=systemd.mount</code>
125
mount options set.</p><p>systemd automatically
126
adds dependencies of type
127
After for this target unit to
128
all SysV init script service
129
units with an LSB header
131
<code class="literal">$local_fs</code>
132
facility.</p></dd><dt><span class="term"><code class="filename">local-fs-pre.target</code></span></dt><dd><p>This target unit is
133
automatically ordered before
134
all local mount points marked
135
with <code class="option">auto</code>
136
(see above). It can be used to
137
execute certain units before
138
all local mounts.</p></dd><dt><span class="term"><code class="filename">mail-transfer-agent.target</code></span></dt><dd><p>The mail transfer agent
139
(MTA) service. Usually this
140
should pull-in all units
142
sending/receiving mails on the
143
local host.</p><p>systemd automatically
144
adds dependencies of type
145
After for this target unit to
146
all SysV init script service
147
units with an LSB header
149
<code class="literal">$mail-transfer-agent</code>
151
<code class="literal">$mail-transport-agent</code>
152
facilities, for compatibility
153
with Debian.</p></dd><dt><span class="term"><code class="filename">multi-user.target</code></span></dt><dd><p>A special target unit
154
for setting up a multi-user
155
system (non-graphical). This
157
<code class="filename">graphical.target</code>.</p><p>Units that are needed
158
for a multi-user system shall
159
add Wants dependencies to
160
this unit for their unit during
161
installation.</p></dd><dt><span class="term"><code class="filename">network.target</code></span></dt><dd><p>systemd automatically
162
adds dependencies of type
163
After for this target unit to
164
all SysV init script service
165
units with an LSB header
167
<code class="literal">$network</code>
168
facility.</p></dd><dt><span class="term"><code class="filename">nss-lookup.target</code></span></dt><dd><p>systemd automatically
169
adds dependencies of type
170
After for this target unit to
171
all SysV init script service
172
units with an LSB header
174
<code class="literal">$named</code>
175
facility.</p></dd><dt><span class="term"><code class="filename">poweroff.target</code></span></dt><dd><p>A special target unit
176
for shutting down and powering off the system.</p><p>Applications wanting to
177
power off the system should start
178
this unit.</p><p><code class="filename">runlevel0.target</code>
179
is an alias for this target
180
unit, for compatibility with SysV.</p></dd><dt><span class="term"><code class="filename">reboot.target</code></span></dt><dd><p>A special target unit
181
for shutting down and rebooting the system.</p><p>Applications wanting to
182
reboot the system should start
183
this unit.</p><p><code class="filename">runlevel6.target</code>
184
is an alias for this target
185
unit, for compatibility with SysV.</p></dd><dt><span class="term"><code class="filename">remote-fs.target</code></span></dt><dd><p>Similar to
186
<code class="filename">local-fs.target</code>,
188
points.</p><p>systemd automatically
189
adds dependencies of type
190
After for this target unit to
191
all SysV init script service
192
units with an LSB header
194
<code class="literal">$remote_fs</code>
195
facility.</p></dd><dt><span class="term"><code class="filename">remote-fs-pre.target</code></span></dt><dd><p>This target unit is
196
automatically ordered before
197
all remote mount points marked
198
with <code class="option">auto</code>
199
(see above). It can be used to
200
execute certain units before
201
all remote mounts.</p></dd><dt><span class="term"><code class="filename">rescue.target</code></span></dt><dd><p>A special target unit
202
for setting up the base system
203
and a rescue shell.</p><p><code class="filename">runlevel1.target</code>
204
is an alias for this target
205
unit, for compatibility with SysV.</p></dd><dt><span class="term"><code class="filename">rpcbind.target</code></span></dt><dd><p>systemd automatically
206
adds dependencies of type
207
After for this target unit to
208
all SysV init script service
209
units with an LSB header
211
<code class="literal">$rpcbind</code>
212
facility.</p></dd><dt><span class="term"><code class="filename">runlevel2.target</code></span></dt><dd><p>This is a target that is
213
called whenever the SysV
214
compatibility code asks for
215
runlevel 2. It is a good idea
216
to make this an alias for
218
<code class="filename">multi-user.target</code>.</p></dd><dt><span class="term"><code class="filename">runlevel3.target</code></span></dt><dd><p>This is a target that is
219
called whenever the SysV
220
compatibility code asks for
221
runlevel 3. It is a good idea
222
to make this an alias for
224
<code class="filename">multi-user.target</code>
226
<code class="filename">graphical.target</code>.</p></dd><dt><span class="term"><code class="filename">runlevel4.target</code></span></dt><dd><p>This is a target that is
227
called whenever the SysV
228
compatibility code asks for
229
runlevel 4. It is a good idea
230
to make this an alias for
232
<code class="filename">multi-user.target</code>
234
<code class="filename">graphical.target</code>.</p></dd><dt><span class="term"><code class="filename">runlevel5.target</code></span></dt><dd><p>This is a target that is
235
called whenever the SysV
236
compatibility code asks for
237
runlevel 5. It is a good idea
238
to make this an alias for
240
<code class="filename">multi-user.target</code>
242
<code class="filename">graphical.target</code>.</p></dd><dt><span class="term"><code class="filename">shutdown.target</code></span></dt><dd><p>A special target unit
243
that terminates the services
244
on system shutdown.</p><p>Services that shall be
245
terminated on system shutdown
247
dependencies to this unit for
248
their service unit, which is
250
<code class="varname">DefaultDependencies=yes</code>
251
is set (the default).</p><p>systemd automatically
252
adds dependencies of type
253
Conflicts to this target unit
254
for all SysV init script
255
service units that shall be
256
terminated in SysV runlevels 0
257
or 6.</p></dd><dt><span class="term"><code class="filename">sigpwr.target</code></span></dt><dd><p>A special target that is
258
started when systemd receives
259
the SIGPWR process signal,
260
which is normally sent by the
261
kernel or UPS daemons when
262
power fails.</p></dd><dt><span class="term"><code class="filename">sockets.target</code></span></dt><dd><p>A special target unit
263
that sets up all service
264
sockets.</p><p>Services that can be
265
socket-activated shall add
266
Wants dependencies to this
267
unit for their socket unit
268
during installation.</p></dd><dt><span class="term"><code class="filename">swap.target</code></span></dt><dd><p>Similar to
269
<code class="filename">local-fs.target</code>, but for swap
271
files.</p></dd><dt><span class="term"><code class="filename">sysinit.target</code></span></dt><dd><p>A special target unit
272
covering early boot-up scripts.</p><p>systemd automatically
273
adds dependencies of the types
274
Wants and After for all
275
SysV service units configured
276
for runlevels that are not 0
277
to 6 to this target unit.
278
This covers the special
279
boot-up runlevels some
280
distributions have, such as S
281
or b.</p></dd><dt><span class="term"><code class="filename">syslog.target</code></span></dt><dd><p>systemd automatically
282
adds dependencies of type
283
After for this target unit to
284
all SysV init script service
285
units with an LSB header
287
<code class="literal">$syslog</code>
288
facility.</p></dd><dt><span class="term"><code class="filename">systemd-initctl.service</code></span></dt><dd><p>This provides
289
compatibility with the SysV
290
/dev/initctl file system FIFO
291
for communication with the
292
init system.</p><p>This is a
293
socket-activated service, see
294
<code class="filename">system-initctl.socket</code>.</p></dd><dt><span class="term"><code class="filename">systemd-initctl.socket</code></span></dt><dd><p>Socket activation unit
296
<code class="filename">system-initctl.service</code>.</p></dd><dt><span class="term"><code class="filename">systemd-stdout-syslog-bridge.service</code></span></dt><dd><p>This is internally used
297
by systemd to provide syslog
298
logging to the processes it
299
maintains.</p><p>This is a
300
socket-activated service, see
301
<code class="filename">system-stdout-syslog-bridge.socket</code>.</p></dd><dt><span class="term"><code class="filename">systemd-stdout-syslog-bridge.socket</code></span></dt><dd><p>Socket activation unit
303
<code class="filename">system-stdout-syslog-bridge.service</code>. systemd
304
will automatically add
305
dependencies of types Requires
306
and After to all units that
307
have been configured for
308
stdout or stderr to be
309
connected to syslog or the
310
kernel log buffer.</p></dd><dt><span class="term"><code class="filename">systemd-shutdownd.service</code></span></dt><dd><p>This is internally used
312
<span class="citerefentry"><span class="refentrytitle">shutdown</span>(8)</span>
313
to implement delayed shutdowns.</p><p>This is a
314
socket-activated service, see
315
<code class="filename">system-shutdownd.socket</code>.</p></dd><dt><span class="term"><code class="filename">systemd-shutdownd.socket</code></span></dt><dd><p>Socket activation unit
317
<code class="filename">system-shutdownd.service</code>.</p></dd><dt><span class="term"><code class="filename">time-sync.target</code></span></dt><dd><p>systemd automatically
318
adds dependencies of type
319
After for this target unit to
320
all SysV init script service
321
units with an LSB header
323
<code class="literal">$time</code>
324
facility.</p></dd><dt><span class="term"><code class="filename">umount.target</code></span></dt><dd><p>A special target unit
325
that umounts all mount and
326
automount points on system
327
shutdown.</p><p>Mounts that shall be
328
unmounted on system shutdown
330
dependencies to this unit for
331
their mount unit, which is
333
<code class="varname">DefaultDependencies=yes</code>
334
is set (the default).</p></dd></dl></div></div><div class="refsect1" title="Special User Units"><a name="id591060"></a><h2>Special User Units</h2><p>When systemd runs as a user instance, the
335
following special units are available, which have
336
similar definitions as their system counterparts:
337
<code class="filename">default.target</code>,
338
<code class="filename">local-fs.target</code>,
339
<code class="filename">remote-fs.target</code>,
340
<code class="filename">shutdown.target</code>,
341
<code class="filename">sockets.target</code>,
342
<code class="filename">swap.target</code>.</p><p>In addition the following special unit is
343
understood only when systemd runs as service instance:</p><div class="variablelist"><dl><dt><span class="term"><code class="filename">exit.service</code></span></dt><dd><p>A special service unit
344
for shutting down the
345
user service manager.</p><p>Applications wanting to
346
terminate the user service
347
manager should start this
348
unit. If systemd receives
349
SIGTERM or SIGINT when running
350
as user service daemon it will
351
start this unit.</p><p>Normally, this pulls in
352
<code class="filename">shutdown.target</code>
353
which in turn should be
354
conflicted by all units that
355
want to be shut down on
356
user service manager exit.</p></dd></dl></div></div><div class="refsect1" title="See Also"><a name="id591144"></a><h2>See Also</h2><p>
357
<span class="citerefentry"><span class="refentrytitle">systemd.unit</span>(5)</span>,
358
<span class="citerefentry"><span class="refentrytitle">systemd.service</span>(5)</span>,
359
<span class="citerefentry"><span class="refentrytitle">systemd.socket</span>(5)</span>,
360
<span class="citerefentry"><span class="refentrytitle">systemd.target</span>(5)</span>
361
</p></div></div></body></html>
added
removed
man/systemd.special.html
