1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
|
<?xml version='1.0'?> <!--*-nxml-*-->
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!--
This file is part of systemd.
Copyright 2010 Lennart Poettering
systemd is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
You should have received a copy of the GNU General Public License
along with systemd; If not, see <http://www.gnu.org/licenses/>.
-->
<refentry id="systemd.special">
<refentryinfo>
<title>systemd.special</title>
<productname>systemd</productname>
<authorgroup>
<author>
<contrib>Developer</contrib>
<firstname>Lennart</firstname>
<surname>Poettering</surname>
<email>lennart@poettering.net</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta>
<refentrytitle>systemd.special</refentrytitle>
<manvolnum>7</manvolnum>
</refmeta>
<refnamediv>
<refname>systemd.special</refname>
<refpurpose>special systemd units</refpurpose>
</refnamediv>
<refsynopsisdiv>
<para><filename>emergency.service</filename></para>
<para><filename>local-fs.target</filename></para>
<para><filename>network.target</filename></para>
<para><filename>nss-lookup.target</filename></para>
<para><filename>remote-fs.target</filename></para>
<para><filename>rpcbind.target</filename></para>
<para><filename>rtc-set.target</filename></para>
<para><filename>shutdown.target</filename></para>
<para><filename>sigpwr.target</filename></para>
<para><filename>sockets.target</filename></para>
<para><filename>swap.target</filename></para>
<para><filename>syslog.target</filename></para>
<para><filename>systemd-initctl.service</filename></para>
<para><filename>systemd-initctl.socket</filename></para>
<para><filename>systemd-logger.service</filename></para>
<para><filename>systemd-logger.socket</filename></para>
</refsynopsisdiv>
<refsect1>
<title>Description</title>
<para>A few units are treated specially by
systemd. They have special internal semantics and
cannot be renamed.</para>
</refsect1>
<refsect1>
<title>Special System Units</title>
<variablelist>
<varlistentry>
<term><filename>emergency.service</filename></term>
<listitem>
<para>A special service unit
that starts an emergency
shell on the main
console. This unit is supposed
to be used with the kernel
command line option
<varname>systemd.default=</varname>
and has otherwise little use.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>local-fs.target</filename></term>
<listitem>
<para>systemd automatically
adds dependencies of type
After to all mount units that
refer to local mount
points. In addition, systemd
adds dependencies of type
Wants to those mounts listed
in
<filename>/etc/fstab</filename>
that have the
<literal>auto</literal> and
<literal>comment=systemd.mount</literal>
mount options set.</para>
<para>systemd automatically
adds dependencies of type
After to this target unit for
all SysV init scripts with an
LSB header referring to the
<literal>$local_fs</literal>
facility.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>network.target</filename></term>
<listitem>
<para>systemd automatically
adds dependencies of type
After to this target unit for
all SysV init scripts with an
LSB header referring to the
<literal>$network</literal>
facility.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>nss-lookup.target</filename></term>
<listitem>
<para>systemd automatically
adds dependencies of type
After to this target unit for
all SysV init scripts with an
LSB header referring to the
<literal>$named</literal>
facility.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>remote-fs.target</filename></term>
<listitem>
<para>Similar to <filename>local-fs.target</filename>, but for remote mount points.</para>
<para>systemd automatically
adds dependencies of type
After to this target unit for
all SysV init scripts with an
LSB header referring to the
<literal>$remote-fs</literal>
facility.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>rpcbind.target</filename></term>
<listitem>
<para>systemd automatically
adds dependencies of type
After to this target unit for
all SysV init scripts with an
LSB header referring to the
<literal>$rpcbind</literal>
facility.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>rtc-set.target</filename></term>
<listitem>
<para>systemd automatically
adds dependencies of type
After to this target unit for
all SysV init scripts with an
LSB header referring to the
<literal>$time</literal>
facility.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>shutdown.target</filename></term>
<listitem>
<para>A special target unit
that terminates the services
on system shutdown.</para>
<para>Services that shall be
terminated on system shutdown
shall add Wants dependencies
from this unit to their
service unit during
installation.</para>
<para>systemd automatically
adds dependencies of type
Conflicts to this target unit
for all SysV init scripts that
shall be terminated in SysV
runlevels 0 or 6.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>sigpwr.target</filename></term>
<listitem>
<para>A special target that is
started when systemd receives
the SIGPWR process signal,
which is normally sent by the
kernel or UPS daemons when the
power fails.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>sockets.target</filename></term>
<listitem>
<para>A special target unit
that sets up all service
sockets.</para>
<para>Services that can be
socket-activated shall add
Wants dependencies from this
unit to their socket unit
during installation.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>swap.target</filename></term>
<listitem>
<para>Similar to
<filename>local-fs.target</filename>, but for swap
partitions and swap
files.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>syslog.target</filename></term>
<listitem>
<para>systemd automatically
adds dependencies of type
After to this target unit for
all SysV init scripts with an
LSB header referring to the
<literal>$syslog</literal>
facility.</para>
<para>Administrators should
ensure that this target pulls
in a service unit with the
name or alias of
<filename>@SPECIAL_SYSLOG_NAME@</filename> (or a
socket unit that activates
this service).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>systemd-initctl.service</filename></term>
<listitem>
<para>This provides
compatibility with the SysV
/dev/initctl file system FIFO
for communication with the
init system.</para>
<para>This is a
socket-activated service, see
<filename>system-initctl.socket</filename>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>systemd-initctl.socket</filename></term>
<listitem>
<para>Socket activation unit
for
<filename>system-initctl.service</filename>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>systemd-logger.service</filename></term>
<listitem>
<para>This is used internally
by systemd to provide syslog
logging to started
processes.</para>
<para>This is a
socket-activated service, see
<filename>system-logger.socket</filename>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>systemd-logger.socket</filename></term>
<listitem>
<para>Socket activation unit
for
<filename>system-logger.service</filename>.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1>
<title>Special Session Units</title>
<para>When systemd runs as a service instance, the
following special units are available, which have
similar definitions as their system counterparts:
<filename>local-fs.target</filename>,
<filename>remote-fs.target</filename>,
<filename>shutdown.target</filename>,
<filename>sockets.target</filename>,
<filename>swap.target</filename>.</para>
</refsect1>
<refsect1>
<title>See Also</title>
<para>
<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>
<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>
<citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry>
<citerefentry><refentrytitle>systemd.target</refentrytitle><manvolnum>5</manvolnum></citerefentry>
</para>
</refsect1>
</refentry>
|