Debian Codegraph @

upstream/fedora-44/man7/systemd.special.7

raw
1 '\" t
2 .TH "SYSTEMD\&.SPECIAL" "7" "" "systemd 259.5" "systemd.special"
3 .\" -----------------------------------------------------------------
4 .\" * Define some portability stuff
5 .\" -----------------------------------------------------------------
6 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7 .\" http://bugs.debian.org/507673
8 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
9 .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
10 .ie \n(.g .ds Aq \(aq
11 .el .ds Aq '
12 .\" -----------------------------------------------------------------
13 .\" * set default formatting
14 .\" -----------------------------------------------------------------
15 .\" disable hyphenation
16 .nh
17 .\" disable justification (adjust text to left margin only)
18 .ad l
19 .\" -----------------------------------------------------------------
20 .\" * MAIN CONTENT STARTS HERE *
21 .\" -----------------------------------------------------------------
22 .SH "NAME"
23 systemd.special \- Special systemd units
24 .SH "SYNOPSIS"
25 .PP
26 basic\&.target,
27 bluetooth\&.target,
28 cryptsetup\-pre\&.target,
29 cryptsetup\&.target,
30 veritysetup\-pre\&.target,
31 veritysetup\&.target,
32 ctrl\-alt\-del\&.target,
33 blockdev@\&.target,
34 boot\-complete\&.target,
35 default\&.target,
36 emergency\&.target,
37 exit\&.target,
38 factory\-reset\&.target,
39 factory\-reset\-now\&.target,
40 final\&.target,
41 first\-boot\-complete\&.target,
42 getty\&.target,
43 getty\-pre\&.target,
44 graphical\&.target,
45 halt\&.target,
46 hibernate\&.target,
47 hybrid\-sleep\&.target,
48 suspend\-then\-hibernate\&.target,
49 initrd\&.target,
50 initrd\-fs\&.target,
51 initrd\-root\-device\&.target,
52 initrd\-root\-fs\&.target,
53 initrd\-usr\-fs\&.target,
54 integritysetup\-pre\&.target,
55 integritysetup\&.target,
56 kbrequest\&.target,
57 kexec\&.target,
58 local\-fs\-pre\&.target,
59 local\-fs\&.target,
60 machines\&.target,
61 multi\-user\&.target,
62 network\-online\&.target,
63 network\-pre\&.target,
64 network\&.target,
65 nss\-lookup\&.target,
66 nss\-user\-lookup\&.target,
67 paths\&.target,
68 poweroff\&.target,
69 printer\&.target,
70 reboot\&.target,
71 remote\-cryptsetup\&.target,
72 remote\-integritysetup\&.target,
73 remote\-veritysetup\&.target,
74 remote\-fs\-pre\&.target,
75 remote\-fs\&.target,
76 rescue\&.target,
77 rpcbind\&.target,
78 shutdown\&.target,
79 sigpwr\&.target,
80 sleep\&.target,
81 slices\&.target,
82 smartcard\&.target,
83 sockets\&.target,
84 soft\-reboot\&.target,
85 sound\&.target,
86 ssh\-access\&.target,
87 storage\-target\-mode\&.target,
88 suspend\&.target,
89 swap\&.target,
90 sysinit\&.target,
91 system\-update\&.target,
92 system\-update\-pre\&.target,
93 time\-set\&.target,
94 time\-sync\&.target,
95 timers\&.target,
96 tpm2\&.target,
97 umount\&.target,
98 usb\-gadget\&.target,
99 \-\&.slice,
100 capsule\&.slice,
101 machine\&.slice,
102 system\&.slice,
103 user\&.slice,
104 \-\&.mount,
105 dbus\&.service,
106 dbus\&.socket,
107 display\-manager\&.service,
108 init\&.scope,
109 syslog\&.socket,
110 system\-update\-cleanup\&.service
111 .SH "DESCRIPTION"
112 .PP
113 A few units are treated specially by systemd\&. Many of them have special internal semantics and cannot be renamed, while others simply have a standard meaning and should be present on all systems\&.
114 .SH "UNITS MANAGED BY THE SYSTEM SERVICE MANAGER"
115 .SS "Special System Units"
116 .PP
117 \-\&.mount
118 .RS 4
119 The root mount point, i\&.e\&. the mount unit for the
120 /
121 path\&. This unit is unconditionally active, during the entire time the system is up, as this mount point is where the basic userspace is running from\&.
122 .sp
123 Added in version 235\&.
124 .RE
125 .PP
126 basic\&.target
127 .RS 4
128 A special target unit covering basic boot\-up\&.
129 .sp
130 systemd automatically adds dependency of the type
131 \fIAfter=\fR
132 for this target unit to all services (except for those with
133 \fIDefaultDependencies=no\fR)\&.
134 .sp
135 Usually, this should pull\-in all local mount points plus
136 /var/,
137 /tmp/
138 and
139 /var/tmp/, swap devices, sockets, timers, path units and other basic initialization necessary for general purpose daemons\&. The mentioned mount points are special cased to allow them to be remote\&.
140 .sp
141 This target usually does not pull in any non\-target units directly, but rather does so indirectly via other early boot targets\&. It is instead meant as a synchronization point for late boot services\&. Refer to
142 \fBbootup\fR(7)
143 for details on the targets involved\&.
144 .RE
145 .PP
146 boot\-complete\&.target
147 .RS 4
148 This target is intended as generic synchronization point for services that shall determine or act on whether the boot process completed successfully\&. Order units that are required to succeed for a boot process to be considered successful before this unit, and add a
149 \fIRequires=\fR
150 dependency from the target unit to them\&. Order units that shall only run when the boot process is considered successful after the target unit and pull in the target from it, also with
151 \fIRequires=\fR\&. Note that by default this target unit is not part of the initial boot transaction, but is supposed to be pulled in only if required by units that want to run only on successful boots\&.
152 .sp
153 See
154 \fBsystemd-boot-check-no-failures.service\fR(8)
155 for a service that implements a generic system health check and orders itself before
156 boot\-complete\&.target\&.
157 .sp
158 See
159 \fBsystemd-bless-boot.service\fR(8)
160 for a service that propagates boot success information to the boot loader, and orders itself after
161 boot\-complete\&.target\&.
162 .sp
163 Added in version 240\&.
164 .RE
165 .PP
166 ctrl\-alt\-del\&.target
167 .RS 4
168 systemd starts this target whenever Control+Alt+Del is pressed on the console\&. Usually, this should be aliased (symlinked) to
169 reboot\&.target\&.
170 .RE
171 .PP
172 cryptsetup\&.target
173 .RS 4
174 A target that pulls in setup services for all encrypted block devices\&.
175 .RE
176 .PP
177 veritysetup\&.target
178 .RS 4
179 A target that pulls in setup services for all verity integrity protected block devices\&.
180 .sp
181 Added in version 248\&.
182 .RE
183 .PP
184 dbus\&.service
185 .RS 4
186 A special unit for the D\-Bus bus daemon\&. As soon as this service is fully started up systemd will connect to it and register its service\&.
187 .RE
188 .PP
189 dbus\&.socket
190 .RS 4
191 A special unit for the D\-Bus system bus socket\&. All units with
192 \fIType=dbus\fR
193 automatically gain a dependency on this unit\&.
194 .RE
195 .PP
196 default\&.target
197 .RS 4
198 The default unit systemd starts at bootup\&. Usually, this should be aliased (symlinked) to
199 multi\-user\&.target
200 or
201 graphical\&.target\&. See
202 \fBbootup\fR(7)
203 for more discussion\&.
204 .sp
205 The default unit systemd starts at bootup can be overridden with the
206 \fIsystemd\&.unit=\fR
207 kernel command line option, or more conveniently, with the short names like
208 \fIsingle\fR,
209 \fIrescue\fR,
210 \fI1\fR,
211 \fI3\fR,
212 \fI5\fR, \&...; see
213 \fBsystemd\fR(1)\&.
214 .sp
215 For typical unit files please set
216 "WantedBy="
217 to a regular target (like
218 multi\-user\&.target
219 or
220 graphical\&.target), instead of
221 default\&.target, since such a service will also be run on special boots like on system update, emergency boot\&...
222 .RE
223 .PP
224 display\-manager\&.service
225 .RS 4
226 The display manager service\&. Usually, this should be aliased (symlinked) to
227 gdm\&.service
228 or a similar display manager service\&.
229 .RE
230 .PP
231 emergency\&.target
232 .RS 4
233 A special target unit that starts an emergency shell on the main console\&. This target does not pull in other services or mounts\&. It is the most minimal version of starting the system in order to acquire an interactive shell; the only processes running are usually just the system manager (PID 1) and the shell process\&. This unit may be used by specifying
234 \fIemergency\fR
235 on the kernel command line; it is also used when a file system check on a required file system fails and boot\-up cannot continue\&. Compare with
236 rescue\&.target, which serves a similar purpose, but also starts the most basic services and mounts all file systems\&.
237 .sp
238 In many ways booting into
239 emergency\&.target
240 is similar to the effect of booting with
241 "init=/bin/sh"
242 on the kernel command line, except that emergency mode provides you with the full system and service manager, and allows starting individual units in order to continue the boot process in steps\&.
243 .sp
244 Note that depending on how
245 emergency\&.target
246 is reached, the root file system might be mounted read\-only or read\-write (no remounting is done specially for this target)\&. For example, the system may boot with root mounted read\-only when
247 \fIro\fR
248 is used on the kernel command line and remain this way for
249 emergency\&.target, or the system may transition to
250 emergency\&.target
251 after the system has been partially booted and disks have already been remounted read\-write\&.
252 .RE
253 .PP
254 exit\&.target
255 .RS 4
256 A special service unit for shutting down the system or user service manager\&. It is equivalent to
257 poweroff\&.target
258 on non\-container systems, and also works in containers\&.
259 .sp
260 systemd will start this unit when it receives the
261 \fBSIGTERM\fR
262 or
263 \fBSIGINT\fR
264 signal when running as user service daemon\&.
265 .sp
266 Normally, this (indirectly) pulls in
267 shutdown\&.target, which in turn should be conflicted by all units that want to be scheduled for shutdown when the service manager starts to exit\&.
268 .sp
269 Added in version 186\&.
270 .RE
271 .PP
272 factory\-reset\&.target
273 .RS 4
274 A special target to request a factory reset operation\&. This will typically persistently store a request flag for the next boot and then reboot in order to reset the system to factory state\&.
275 .sp
276 See
277 \m[blue]\fBFactory Reset\fR\m[]\&\s-2\u[1]\d\s+2
278 for more information\&.
279 .sp
280 Added in version 250\&.
281 .RE
282 .PP
283 factory\-reset\-now\&.target
284 .RS 4
285 A special target that is started on boots that shall execute a factory reset\&. It may be used to pull in additional services that shall be invoked during a factory reset operation\&. It also acts as ordering barrier: once the target is reached the factory reset state is marked as "completed"\&.
286 .sp
287 See
288 \m[blue]\fBFactory Reset\fR\m[]\&\s-2\u[1]\d\s+2
289 for more information\&.
290 .sp
291 Added in version 258\&.
292 .RE
293 .PP
294 final\&.target
295 .RS 4
296 A special target unit that is used during the shutdown logic and may be used to pull in late services after all normal services are already terminated and all mounts unmounted\&.
297 .RE
298 .PP
299 getty\&.target
300 .RS 4
301 A special target unit that pulls in statically configured local TTY
302 getty
303 instances\&.
304 .RE
305 .PP
306 graphical\&.target
307 .RS 4
308 A special target unit for setting up a graphical login screen\&. This pulls in
309 multi\-user\&.target\&.
310 .sp
311 Units that are needed for graphical logins shall add
312 \fIWants=\fR
313 dependencies for their unit to this unit (or
314 multi\-user\&.target) during installation\&. This is best configured via
315 \fIWantedBy=graphical\&.target\fR
316 in the unit\*(Aqs [Install] section\&.
317 .RE
318 .PP
319 hibernate\&.target
320 .RS 4
321 A special target unit for hibernating the system\&. This pulls in
322 sleep\&.target\&.
323 .RE
324 .PP
325 hybrid\-sleep\&.target
326 .RS 4
327 A special target unit for hibernating and suspending the system at the same time\&. This pulls in
328 sleep\&.target\&.
329 .sp
330 Added in version 196\&.
331 .RE
332 .PP
333 suspend\-then\-hibernate\&.target
334 .RS 4
335 A special target unit for suspending the system for a period of time, waking it and putting it into hibernate\&. This pulls in
336 sleep\&.target\&.
337 .sp
338 Added in version 239\&.
339 .RE
340 .PP
341 halt\&.target
342 .RS 4
343 A special target unit for shutting down and halting the system\&. Note that this target is distinct from
344 poweroff\&.target
345 in that it generally really just halts the system rather than powering it down\&.
346 .sp
347 Applications wanting to halt the system should not start this unit directly, but should instead execute
348 \fBsystemctl halt\fR
349 (possibly with the
350 \fB\-\-no\-block\fR
351 option) or call
352 \fBsystemd\fR(1)\*(Aqs
353 \fBorg\&.freedesktop\&.systemd1\&.Manager\&.Halt\fR
354 D\-Bus method directly\&.
355 .RE
356 .PP
357 imports\&.target
358 .RS 4
359 A target unit that pulls in all disk image download jobs to execute on system boot\&. This is used by
360 \fBsystemd-import-generator\fR(8)\&.
361 .sp
362 Added in version 258\&.
363 .RE
364 .PP
365 init\&.scope
366 .RS 4
367 This scope unit is where the system and service manager (PID 1) itself resides\&. It is active as long as the system is running\&.
368 .sp
369 Added in version 235\&.
370 .RE
371 .PP
372 initrd\&.target
373 .RS 4
374 This is the default target in the initrd, similar to
375 default\&.target
376 in the main system\&. It is used to mount the real root and transition to it\&. See
377 \fBbootup\fR(7)
378 for more discussion\&.
379 .sp
380 Added in version 245\&.
381 .RE
382 .PP
383 initrd\-fs\&.target
384 .RS 4
385 \fBsystemd-fstab-generator\fR(8)
386 automatically adds dependencies of type
387 \fIBefore=\fR
388 to
389 sysroot\-usr\&.mount
390 and all mount points found in
391 /etc/fstab
392 that have the
393 \fBx\-initrd\&.mount\fR
394 mount option set and do not have the
395 \fBnoauto\fR
396 mount option set\&. It is also indirectly ordered after
397 sysroot\&.mount\&. Thus, once this target is reached the
398 /sysroot/
399 hierarchy is fully set up, in preparation for the transition to the host OS\&.
400 .sp
401 Added in version 199\&.
402 .RE
403 .PP
404 initrd\-root\-device\&.target
405 .RS 4
406 A special initrd target unit that is reached when the root filesystem device is available, but before it has been mounted\&.
407 \fBsystemd-fstab-generator\fR(8)
408 and
409 \fBsystemd-gpt-auto-generator\fR(8)
410 automatically set up the appropriate dependencies to make this happen\&.
411 .sp
412 Added in version 230\&.
413 .RE
414 .PP
415 initrd\-root\-fs\&.target
416 .RS 4
417 \fBsystemd-fstab-generator\fR(8)
418 automatically adds dependencies of type
419 \fIBefore=\fR
420 to the
421 sysroot\&.mount
422 unit, which is generated from the kernel command line\*(Aqs
423 \fIroot=\fR
424 setting (or equivalent)\&.
425 .sp
426 Added in version 199\&.
427 .RE
428 .PP
429 initrd\-usr\-fs\&.target
430 .RS 4
431 \fBsystemd-fstab-generator\fR(8)
432 automatically adds dependencies of type
433 \fIBefore=\fR
434 to the
435 sysusr\-usr\&.mount
436 unit, which is generated from the kernel command line\*(Aqs
437 \fIusr=\fR
438 switch\&. Services may order themselves after this target unit in order to run once the
439 /sysusr/
440 hierarchy becomes available, on systems that come up initially without a root file system, but with an initialized
441 /usr/
442 and need to access that before setting up the root file system to ultimately switch to\&. On systems where
443 \fIusr=\fR
444 is not used this target is ordered after
445 sysroot\&.mount
446 and thus mostly equivalent to
447 initrd\-root\-fs\&.target\&. In effect on any system once this target is reached the file system backing
448 /usr/
449 is mounted, though possibly at two different locations, either below the
450 /sysusr/
451 or the
452 /sysroot/
453 hierarchies\&.
454 .sp
455 Added in version 249\&.
456 .RE
457 .PP
458 kbrequest\&.target
459 .RS 4
460 systemd starts this target whenever Alt+ArrowUp is pressed on the console\&. Note that any user with physical access to the machine will be able to do this, without authentication, so this should be used carefully\&.
461 .RE
462 .PP
463 kexec\&.target
464 .RS 4
465 A special target unit for shutting down and rebooting the system via kexec\&.
466 .sp
467 Applications wanting to reboot the system should not start this unit directly, but should instead execute
468 \fBsystemctl kexec\fR
469 (possibly with the
470 \fB\-\-no\-block\fR
471 option) or call
472 \fBsystemd-logind\fR(8)\*(Aqs
473 \fBorg\&.freedesktop\&.login1\&.Manager\&.RebootWithFlags()\fR
474 D\-Bus method directly\&.
475 .sp
476 See
477 \fBsystemd-kexec.service\fR(8)
478 for further details of the operation this target pulls in\&.
479 .RE
480 .PP
481 local\-fs\&.target
482 .RS 4
483 \fBsystemd-fstab-generator\fR(8)
484 automatically adds dependencies of type
485 \fIBefore=\fR
486 to all mount units that refer to local mount points for this target unit\&. In addition, it adds dependencies of type
487 \fIWants=\fR
488 to this target unit for those mounts listed in
489 /etc/fstab
490 that have the
491 \fBauto\fR
492 mount option set\&.
493 .RE
494 .PP
495 machines\&.target
496 .RS 4
497 A standard target unit for starting all the containers and other virtual machines\&. See
498 systemd\-nspawn@\&.service
499 for an example\&.
500 .sp
501 Added in version 233\&.
502 .RE
503 .PP
504 multi\-user\&.target
505 .RS 4
506 A special target unit for setting up a multi\-user system (non\-graphical)\&. This is pulled in by
507 graphical\&.target\&.
508 .sp
509 Units that are needed for a multi\-user system shall add
510 \fIWants=\fR
511 dependencies for their unit to this unit during installation\&. This is best configured via
512 \fIWantedBy=multi\-user\&.target\fR
513 in the unit\*(Aqs [Install] section\&.
514 .RE
515 .PP
516 network\-online\&.target
517 .RS 4
518 Units that strictly require a configured network connection should pull in
519 network\-online\&.target
520 (via a
521 \fIWants=\fR
522 type dependency) and order themselves after it\&. This target unit is intended to pull in a service that delays further execution until the network is sufficiently set up\&. What precisely this requires is left to the implementation of the network managing service\&.
523 .sp
524 Note the distinction between this unit and
525 network\&.target\&. This unit is an active unit (i\&.e\&. pulled in by the consumer rather than the provider of this functionality) and pulls in a service which possibly adds substantial delays to further execution\&. In contrast,
526 network\&.target
527 is a passive unit (i\&.e\&. pulled in by the provider of the functionality, rather than the consumer) that usually does not delay execution much\&. Usually,
528 network\&.target
529 is part of the boot of most systems, while
530 network\-online\&.target
531 is not, except when at least one unit requires it\&. Also see
532 \m[blue]\fBRunning Services After the Network Is Up\fR\m[]\&\s-2\u[2]\d\s+2
533 for more information\&.
534 .sp
535 All mount units for remote network file systems automatically pull in this unit, and order themselves after it\&. Note that networking daemons that simply
536 \fIprovide\fR
537 functionality to other hosts (as opposed to
538 \fIconsume\fR
539 functionality of other hosts) generally do not need to pull this in\&.
540 .sp
541 systemd automatically adds dependencies of type
542 \fIWants=\fR
543 and
544 \fIAfter=\fR
545 for this target unit to all SysV init script service units with an LSB header referring to the
546 "$network"
547 facility\&.
548 .sp
549 Note that this unit is only useful during the original system start\-up logic\&. After the system has completed booting up, it will not track the online state of the system anymore\&. Due to this it cannot be used as a network connection monitor concept, it is purely a one\-time system start\-up concept\&.
550 .sp
551 Added in version 200\&.
552 .RE
553 .PP
554 paths\&.target
555 .RS 4
556 A special target unit that sets up all path units (see
557 \fBsystemd.path\fR(5)
558 for details) that shall be active after boot\&.
559 .sp
560 It is recommended that path units installed by applications get pulled in via
561 \fIWants=\fR
562 dependencies from this unit\&. This is best configured via a
563 \fIWantedBy=paths\&.target\fR
564 in the path unit\*(Aqs [Install] section\&.
565 .sp
566 Added in version 199\&.
567 .RE
568 .PP
569 poweroff\&.target
570 .RS 4
571 A special target unit for shutting down and powering off the system\&.
572 .sp
573 Applications wanting to power off the system should not start this unit directly, but should instead execute
574 \fBsystemctl poweroff\fR
575 (possibly with the
576 \fB\-\-no\-block\fR
577 option) or call
578 \fBsystemd-logind\fR(8)\*(Aqs
579 \fBorg\&.freedesktop\&.login1\&.Manager\&.PowerOff\fR
580 D\-Bus method directly\&.
581 .RE
582 .PP
583 reboot\&.target
584 .RS 4
585 A special target unit for shutting down and rebooting the system\&.
586 .sp
587 Applications wanting to reboot the system should not start this unit directly, but should instead execute
588 \fBsystemctl reboot\fR
589 (possibly with the
590 \fB\-\-no\-block\fR
591 option) or call
592 \fBsystemd-logind\fR(8)\*(Aqs
593 \fBorg\&.freedesktop\&.login1\&.Manager\&.Reboot()\fR
594 D\-Bus method directly\&.
595 .sp
596 See
597 \fBsystemd-reboot.service\fR(8)
598 for further details of the operation this target pulls in\&.
599 .RE
600 .PP
601 remote\-cryptsetup\&.target
602 .RS 4
603 Similar to
604 cryptsetup\&.target, but for encrypted devices which are accessed over the network\&. It is used for
605 \fBcrypttab\fR(5)
606 entries marked with
607 \fB_netdev\fR\&.
608 .sp
609 Added in version 235\&.
610 .RE
611 .PP
612 remote\-integritysetup\&.target
613 .RS 4
614 Similar to
615 integritysetup\&.target, but for integrity protected devices which are accessed over the network\&. It is used for
616 \fBintegritytab\fR(5)
617 entries marked with
618 \fB_netdev\fR\&.
619 .sp
620 Added in version 258\&.
621 .RE
622 .PP
623 remote\-veritysetup\&.target
624 .RS 4
625 Similar to
626 veritysetup\&.target, but for verity protected devices which are accessed over the network\&. It is used for
627 \fBveritytab\fR(5)
628 entries marked with
629 \fB_netdev\fR\&.
630 .sp
631 Added in version 248\&.
632 .RE
633 .PP
634 remote\-fs\&.target
635 .RS 4
636 Similar to
637 local\-fs\&.target, but for remote mount points\&.
638 .sp
639 systemd automatically adds dependencies of type
640 \fIAfter=\fR
641 for this target unit to all SysV init script service units with an LSB header referring to the
642 "$remote_fs"
643 facility\&.
644 .RE
645 .PP
646 rescue\&.target
647 .RS 4
648 A special target unit that pulls in the base system (including system mounts) and spawns a rescue shell\&. Isolate to this target in order to administer the system in single\-user mode with all file systems mounted but with no services running, except for the most basic\&. Compare with
649 emergency\&.target, which is much more reduced and does not provide the file systems or most basic services\&. Compare with
650 multi\-user\&.target, this target could be seen as
651 single\-user\&.target\&.
652 .sp
653 Use the
654 "systemd\&.unit=rescue\&.target"
655 kernel command line option to boot into this mode\&. A short alias for this kernel command line option is
656 "1", for compatibility with SysV\&.
657 .RE
658 .PP
659 shutdown\&.target
660 .RS 4
661 A special target unit that terminates the services on system shutdown\&.
662 .sp
663 Services that shall be terminated on system shutdown shall add
664 \fIConflicts=\fR
665 and
666 \fIBefore=\fR
667 dependencies to this unit for their service unit, which is implicitly done when
668 \fIDefaultDependencies=yes\fR
669 is set (the default)\&.
670 .RE
671 .PP
672 sigpwr\&.target
673 .RS 4
674 A special target that is started when systemd receives the SIGPWR process signal, which is normally sent by the kernel or UPS daemons when power fails\&.
675 .RE
676 .PP
677 sleep\&.target
678 .RS 4
679 A special target unit that is pulled in by
680 suspend\&.target,
681 hibernate\&.target,
682 suspend\-then\-hibernate\&.target, and
683 hybrid\-sleep\&.target
684 and may be used to hook units into the sleep state logic\&.
685 .sp
686 In order to hook external programs
687 \fIbefore\fR
688 the actual system sleep operation, place their command line in a service unit file\*(Aqs
689 \fIExecStart=\fR
690 line (use
691 \fIType=oneshot\fR), and ensure the unit is pulled in by
692 sleep\&.target
693 and ordered before it\&. In order to hook program code
694 \fIafter\fR
695 the actual system sleep operation (i\&.e\&. to be run after the system woke up again), place the command in
696 \fIExecStop=\fR
697 instead, and make sure to enable
698 \fIStopWhenUnneeded=\fR
699 and
700 \fIRemainAfterExit=\fR\&. Both approaches can be combined into one unit file in order to run programs both before and after the sleep operation\&.
701 .PP
702 \fBExample\ \&1.\ \&Combined Example\fR
703 .sp
704 .if n \{\
705 .RS 4
706 .\}
707 .nf
708 [Unit]
709 DefaultDependencies=no
710 StopWhenUnneeded=yes
711 Before=sleep\&.target
712
713 [Service]
714 Type=oneshot
715 RemainAfterExit=yes
716 ExecStart=/usr/bin/some\-before\-command
717 ExecStop=/Usr/bin/some\-after\-command
718
719 [Install]
720 WantedBy=sleep\&.target
721 .fi
722 .if n \{\
723 .RE
724 .\}
725 .RE
726 .PP
727 slices\&.target
728 .RS 4
729 A special target unit that sets up all slice units (see
730 \fBsystemd.slice\fR(5)
731 for details) that shall always be active after boot\&. By default, the generic
732 system\&.slice
733 slice unit as well as the root slice unit
734 \-\&.slice
735 are pulled in and ordered before this unit (see below)\&.
736 .sp
737 Adding slice units to
738 slices\&.target
739 is generally not necessary\&. Instead, when some unit that uses
740 \fISlice=\fR
741 is started, the specified slice will be started automatically\&. Adding
742 \fIWantedBy=slices\&.target\fR
743 lines to the [Install] section should only be done for units that need to be always active\&. In that case care needs to be taken to avoid creating a loop through the automatic dependencies on "parent" slices\&.
744 .sp
745 Added in version 229\&.
746 .RE
747 .PP
748 sockets\&.target
749 .RS 4
750 A special target unit that sets up all socket units (see
751 \fBsystemd.socket\fR(5)
752 for details) that shall be active after boot\&.
753 .sp
754 Services that can be socket\-activated shall add
755 \fIWants=\fR
756 dependencies to this unit for their socket unit during installation\&. This is best configured via a
757 \fIWantedBy=sockets\&.target\fR
758 in the socket unit\*(Aqs [Install] section\&.
759 .RE
760 .PP
761 soft\-reboot\&.target
762 .RS 4
763 A special target unit for shutting down and rebooting the userspace of the system (leaving the kernel running)\&.
764 .sp
765 Applications wanting to reboot the system should not start this unit directly, but should instead execute
766 \fBsystemctl soft\-reboot\fR
767 (possibly with the
768 \fB\-\-no\-block\fR
769 option) or call
770 \fBsystemd-logind\fR(8)\*(Aqs
771 \fBorg\&.freedesktop\&.login1\&.Manager\&.RebootWithFlags()\fR
772 D\-Bus method directly\&.
773 .sp
774 See
775 \fBsystemd-soft-reboot.service\fR(8)
776 for further details of the operation this target pulls in\&.
777 .sp
778 Added in version 254\&.
779 .RE
780 .PP
781 storage\-target\-mode\&.target
782 .RS 4
783 A special target unit that can be booted into that selects the "Storage Target Mode" for the OS\&. In this mode all local storage disks are exposed to external systems as block devices\&. This invokes
784 \fBsystemd-storagetm.service\fR(8)
785 which exposes all local disks as NVMe\-TCP devices for access over the network\&. It might as well invoke other services too that make local disks available via other mechanisms\&.
786 .sp
787 Added in version 255\&.
788 .RE
789 .PP
790 suspend\&.target
791 .RS 4
792 A special target unit for suspending the system\&. This pulls in
793 sleep\&.target\&.
794 .RE
795 .PP
796 swap\&.target
797 .RS 4
798 Similar to
799 local\-fs\&.target, but for swap partitions and swap files\&.
800 .RE
801 .PP
802 sysinit\&.target
803 .RS 4
804 systemd automatically adds dependencies of the types
805 \fIRequires=\fR
806 and
807 \fIAfter=\fR
808 for this target unit to all services (except for those with
809 \fIDefaultDependencies=no\fR)\&.
810 .sp
811 This target pulls in the services required for system initialization\&. System services pulled in by this target should declare
812 \fIDefaultDependencies=no\fR
813 and specify all their dependencies manually, including access to anything more than a read only root filesystem\&. For details on the dependencies of this target, refer to
814 \fBbootup\fR(7)\&.
815 .RE
816 .PP
817 syslog\&.socket
818 .RS 4
819 The socket unit syslog implementations should listen on\&. All userspace log messages will be made available on this socket\&. For more information about syslog integration, please consult the
820 \m[blue]\fBSyslog Interface\fR\m[]\&\s-2\u[3]\d\s+2
821 document\&.
822 .RE
823 .PP
824 system\-update\&.target, system\-update\-pre\&.target, system\-update\-cleanup\&.service
825 .RS 4
826 A special target unit that is used for offline system updates\&.
827 \fBsystemd-system-update-generator\fR(8)
828 will redirect the boot process to this target if
829 /system\-update
830 or
831 /etc/system\-update
832 exists\&. For more information see
833 \fBsystemd.offline-updates\fR(7)\&.
834 .sp
835 Updates should happen before the
836 system\-update\&.target
837 is reached, and the services which implement them should cause the machine to reboot\&. The main units executing the update should order themselves after
838 system\-update\-pre\&.target
839 but not pull it in\&. Services which want to run during system updates only, but before the actual system update is executed should order themselves before this unit and pull it in\&. As a safety measure, if this does not happen, and
840 /system\-update
841 or
842 /etc/system\-update
843 still exists after
844 system\-update\&.target
845 is reached,
846 system\-update\-cleanup\&.service
847 will remove the symlinks and reboot the machine\&.
848 .sp
849 Added in version 186\&.
850 .RE
851 .PP
852 timers\&.target
853 .RS 4
854 A special target unit that sets up all timer units (see
855 \fBsystemd.timer\fR(5)
856 for details) that shall be active after boot\&.
857 .sp
858 It is recommended that timer units installed by applications get pulled in via
859 \fIWants=\fR
860 dependencies from this unit\&. This is best configured via
861 \fIWantedBy=timers\&.target\fR
862 in the timer unit\*(Aqs [Install] section\&.
863 .sp
864 Added in version 199\&.
865 .RE
866 .PP
867 umount\&.target
868 .RS 4
869 A special target unit that unmounts all mount and automount points on system shutdown\&.
870 .sp
871 Mounts that shall be unmounted on system shutdown shall add Conflicts dependencies to this unit for their mount unit, which is implicitly done when
872 \fIDefaultDependencies=yes\fR
873 is set (the default)\&.
874 .RE
875 .SS "Special System Units for Devices"
876 .PP
877 Some target units are automatically pulled in as devices of certain kinds show up in the system\&. These may be used to automatically activate various services based on the specific type of the available hardware\&.
878 .PP
879 bluetooth\&.target
880 .RS 4
881 This target is started automatically as soon as a Bluetooth controller is plugged in or becomes available at boot\&.
882 .sp
883 This may be used to pull in Bluetooth management daemons dynamically when Bluetooth hardware is found\&.
884 .RE
885 .PP
886 printer\&.target
887 .RS 4
888 This target is started automatically as soon as a printer is plugged in or becomes available at boot\&.
889 .sp
890 This may be used to pull in printer management daemons dynamically when printer hardware is found\&.
891 .RE
892 .PP
893 smartcard\&.target
894 .RS 4
895 This target is started automatically as soon as a smartcard controller is plugged in or becomes available at boot\&.
896 .sp
897 This may be used to pull in smartcard management daemons dynamically when smartcard hardware is found\&.
898 .RE
899 .PP
900 sound\&.target
901 .RS 4
902 This target is started automatically as soon as a sound card is plugged in or becomes available at boot\&.
903 .sp
904 This may be used to pull in audio management daemons dynamically when audio hardware is found\&.
905 .RE
906 .PP
907 usb\-gadget\&.target
908 .RS 4
909 This target is started automatically as soon as a USB Device Controller becomes available at boot\&.
910 .sp
911 This may be used to pull in usb gadget dynamically when UDC hardware is found\&.
912 .sp
913 Added in version 242\&.
914 .RE
915 .PP
916 tpm2\&.target
917 .RS 4
918 This target is started automatically if a TPM2 device is discovered, either by the OS or by the firmware\&. It acts as synchronization point for services that require TPM2 device access\&. The target unit is enqueued by
919 \fBsystemd-tpm2-generator\fR(8)
920 if it detects that the firmware has discovered a TPM2 device but the OS kernel has not activated a driver for it yet\&. It is also pulled in whenever
921 \fBsystemd-udevd.service\fR(8)
922 discovers a TPM2 device\&. The target unit is ordered after the
923 /dev/tpmrm0
924 device node, so that it only becomes active once the TPM2 device is actually accessible\&. Early boot programs that intend to access the TPM2 device should hence order themselves after this target unit, but not pull it in\&.
925 .sp
926 Added in version 256\&.
927 .RE
928 .SS "Special Passive System Units"
929 .PP
930 A number of special system targets are defined that can be used to properly order boot\-up of optional services\&. These targets are generally not part of the initial boot transaction, unless they are explicitly pulled in by one of the implementing services\&. Note specifically that these
931 \fIpassive\fR
932 target units are generally not pulled in by the consumer of a service, but by the provider of the service\&. This means: a consuming service should order itself after these targets (as appropriate), but not pull it in\&. A providing service should order itself before these targets (as appropriate) and pull it in (via a
933 \fIWants=\fR
934 type dependency)\&.
935 .PP
936 Note that these passive units cannot be started manually, i\&.e\&.
937 "systemctl start time\-sync\&.target"
938 will fail with an error\&. They can only be pulled in by dependency\&. This is enforced since they exist for ordering purposes only and thus are not useful as only unit within a transaction\&.
939 .PP
940 blockdev@\&.target
941 .RS 4
942 This template unit is used to order mount units and other consumers of block devices after services that synthesize these block devices\&. In particular, this is intended to be used with storage services (such as
943 \[email protected]\fR(5)/
944 \[email protected]\fR(8)) that allocate and manage a virtual block device\&. Storage services are ordered before an instance of
945 blockdev@\&.target, and the consumer units after it\&. The ordering is particularly relevant during shutdown, as it ensures that the mount is deactivated first and the service backing the mount later\&. The
946 blockdev@\&.target
947 instance should be pulled in via a
948 \fBWants=\fR
949 dependency of the storage daemon and thus generally not be part of any transaction unless a storage daemon is used\&. The instance name for instances of this template unit must be a properly escaped block device node path, e\&.g\&.
950 blockdev@dev\-mapper\-foobar\&.target
951 for the storage device
952 /dev/mapper/foobar\&.
953 .sp
954 Added in version 245\&.
955 .RE
956 .PP
957 cryptsetup\-pre\&.target
958 .RS 4
959 This passive target unit may be pulled in by services that want to run before any encrypted block device is set up\&. All encrypted block devices are set up after this target has been reached\&. Since the shutdown order is implicitly the reverse start\-up order between units, this target is particularly useful to ensure that a service is shut down only after all encrypted block devices are fully stopped\&.
960 .sp
961 Added in version 215\&.
962 .RE
963 .PP
964 veritysetup\-pre\&.target
965 .RS 4
966 This passive target unit may be pulled in by services that want to run before any verity integrity protected block device is set up\&. All verity integrity protected block devices are set up after this target has been reached\&. Since the shutdown order is implicitly the reverse start\-up order between units, this target is particularly useful to ensure that a service is shut down only after all verity integrity protected block devices are fully stopped\&.
967 .sp
968 Added in version 248\&.
969 .RE
970 .PP
971 first\-boot\-complete\&.target
972 .RS 4
973 This passive target is intended as a synchronization point for units that need to run once during the first boot\&. Only after all units ordered before this target have finished, will the
974 \fBmachine-id\fR(5)
975 be committed to disk, marking the first boot as completed\&. If the boot is aborted at any time before that, the next boot will re\-run any units with
976 \fIConditionFirstBoot=yes\fR\&.
977 .sp
978 Added in version 247\&.
979 .RE
980 .PP
981 getty\-pre\&.target
982 .RS 4
983 A special passive target unit\&. Users of this target are expected to pull it in the boot transaction via a dependency (e\&.g\&.
984 \fIWants=\fR)\&. Order your unit before this unit if you want to make use of the console just before
985 getty
986 is started\&.
987 .sp
988 Added in version 235\&.
989 .RE
990 .PP
991 imports\-pre\&.target
992 .RS 4
993 A passive unit that is ordered before all disk image download jobs to execute on system boot\&. This is used by
994 \fBsystemd-import-generator\fR(8)\&.
995 .sp
996 Added in version 258\&.
997 .RE
998 .PP
999 local\-fs\-pre\&.target
1000 .RS 4
1001 This target unit is automatically ordered before all local mount points marked with
1002 \fBauto\fR
1003 (see above)\&. It can be used to execute certain units before all local mounts\&.
1004 .RE
1005 .PP
1006 network\&.target
1007 .RS 4
1008 This unit is supposed to indicate when network functionality is available, but it is only very weakly defined what that is supposed to mean\&. However, the following should apply at minimum:
1009 .sp
1010 .RS 4
1011 .ie n \{\
1012 \h'-04'\(bu\h'+03'\c
1013 .\}
1014 .el \{\
1015 .sp -1
1016 .IP \(bu 2.3
1017 .\}
1018 At start\-up, any configured synthetic network devices (i\&.e\&. not physical ones that require hardware to show up and be probed, but virtual ones like bridge devices and similar which are created programmatically) that do not depend on any underlying hardware should be allocated by the time this target is reached\&. It is not necessary for these interfaces to also have completed IP level configuration by the time
1019 network\&.target
1020 is reached\&.
1021 .RE
1022 .sp
1023 .RS 4
1024 .ie n \{\
1025 \h'-04'\(bu\h'+03'\c
1026 .\}
1027 .el \{\
1028 .sp -1
1029 .IP \(bu 2.3
1030 .\}
1031 At shutdown, a unit that is ordered after
1032 network\&.target
1033 will be stopped before the network \(em to whatever level it might be set up by then \(em is shut down\&. It is hence useful when writing service files that require network access on shutdown, which should order themselves after this target, but not pull it in\&. Also see
1034 \m[blue]\fBRunning Services After the Network Is Up\fR\m[]\&\s-2\u[2]\d\s+2
1035 for more information\&.
1036 .RE
1037 .sp
1038 It must emphasized that at start\-up there\*(Aqs no guarantee that hardware\-based devices have shown up by the time this target is reached, or even acquired complete IP configuration\&. For that purpose use
1039 network\-online\&.target
1040 as described above\&.
1041 .RE
1042 .PP
1043 network\-pre\&.target
1044 .RS 4
1045 This passive target unit may be pulled in by services that want to run before any network is set up, for example for the purpose of setting up a firewall\&. All network management software orders itself after this target, but does not pull it in\&. Also see
1046 \m[blue]\fBRunning Services After the Network Is Up\fR\m[]\&\s-2\u[2]\d\s+2
1047 for more information\&.
1048 .sp
1049 Added in version 214\&.
1050 .RE
1051 .PP
1052 nss\-lookup\&.target
1053 .RS 4
1054 A target that should be used as synchronization point for all host/network name service lookups\&. Note that this is independent of UNIX user/group name lookups for which
1055 nss\-user\-lookup\&.target
1056 should be used\&. All services for which the availability of full host/network name resolution is essential should be ordered after this target, but not pull it in\&. systemd automatically adds dependencies of type
1057 \fIAfter=\fR
1058 for this target unit to all SysV init script service units with an LSB header referring to the
1059 "$named"
1060 facility\&.
1061 .RE
1062 .PP
1063 nss\-user\-lookup\&.target
1064 .RS 4
1065 A target that should be used as synchronization point for all regular UNIX user/group name service lookups\&. Note that this is independent of host/network name lookups for which
1066 nss\-lookup\&.target
1067 should be used\&. All services for which the availability of the full user/group database is essential should be ordered after this target, but not pull it in\&. All services which provide parts of the user/group database should be ordered before this target, and pull it in\&. Note that this unit is only relevant for regular users and groups \(em system users and groups are required to be resolvable during earliest boot already, and hence do not need any special ordering against this target\&.
1068 .RE
1069 .PP
1070 remote\-fs\-pre\&.target
1071 .RS 4
1072 This target unit is automatically ordered before all mount point units (see above) and cryptsetup/veritysetup devices marked with the
1073 \fB_netdev\fR\&. It can be used to run certain units before remote encrypted devices and mounts are established\&. Note that this unit is generally not part of the initial transaction, unless the unit that wants to be ordered before all remote mounts pulls it in via a
1074 \fIWants=\fR
1075 type dependency\&. If the unit wants to be pulled in by the first remote mount showing up, it should use
1076 network\-online\&.target
1077 (see above)\&.
1078 .RE
1079 .PP
1080 rpcbind\&.target
1081 .RS 4
1082 The portmapper/rpcbind pulls in this target and orders itself before it, to indicate its availability\&. systemd automatically adds dependencies of type
1083 \fIAfter=\fR
1084 for this target unit to all SysV init script service units with an LSB header referring to the
1085 "$portmap"
1086 facility\&.
1087 .RE
1088 .PP
1089 ssh\-access\&.target
1090 .RS 4
1091 Service and socket units that provide remote SSH secure shell access to the local system should pull in this unit and order themselves before this unit\&. It\*(Aqs supposed to act as a milestone indicating if and when SSH access into the system is available\&. It should only become active when an SSH port is bound for remote clients (i\&.e\&. if SSH is used as a local privilege escalation mechanism, it should
1092 \fInot\fR
1093 involve this target unit), regardless of the protocol choices, i\&.e\&. regardless of whether IPv4, IPv6 or
1094 \fBAF_VSOCK\fR
1095 is used\&.
1096 .sp
1097 Added in version 256\&.
1098 .RE
1099 .PP
1100 time\-set\&.target
1101 .RS 4
1102 Services responsible for setting the system clock (\fBCLOCK_REALTIME\fR) from a local source (such as a maintained timestamp file or imprecise real\-time clock) should pull in this target and order themselves before it\&. Services where approximate, roughly monotonic time is desired should be ordered after this unit, but not pull it in\&.
1103 .sp
1104 This target does not provide the accuracy guarantees of
1105 time\-sync\&.target
1106 (see below), however does not depend on remote clock sources to be reachable, i\&.e\&. the target is typically not delayed by network problems and similar\&. Use of this target is recommended for services where approximate clock accuracy and rough monotonicity is desired but activation shall not be delayed for possibly unreliable network communication\&.
1107 .sp
1108 The service manager automatically adds dependencies of type
1109 \fIAfter=\fR
1110 for this target unit to all timer units with at least one
1111 \fIOnCalendar=\fR
1112 directive\&.
1113 .sp
1114 The
1115 \fBsystemd-timesyncd.service\fR(8)
1116 service is a simple daemon that pulls in this target and orders itself before it\&. Besides implementing the SNTP network protocol it maintains a timestamp file on disk whose modification time is regularly updated\&. At service start\-up the local system clock is set from that modification time, ensuring it increases roughly monotonically\&.
1117 .sp
1118 Note that ordering a unit after
1119 time\-set\&.target
1120 only has effect if there\*(Aqs actually a service ordered before it that delays it until the clock is adjusted for rough monotonicity\&. Otherwise, this target might get reached before the clock is adjusted to be roughly monotonic\&. Enable
1121 \fBsystemd-timesyncd.service\fR(8), or an alternative NTP implementation to delay the target\&.
1122 .sp
1123 Added in version 242\&.
1124 .RE
1125 .PP
1126 time\-sync\&.target
1127 .RS 4
1128 Services indicating completed synchronization of the system clock (\fBCLOCK_REALTIME\fR) to a remote source should pull in this target and order themselves before it\&. Services where accurate time is essential should be ordered after this unit, but not pull it in\&.
1129 .sp
1130 The service manager automatically adds dependencies of type
1131 \fIAfter=\fR
1132 for this target unit to all SysV init script service units with an LSB header referring to the
1133 "$time"
1134 facility, as well to all timer units with at least one
1135 \fIOnCalendar=\fR
1136 directive\&.
1137 .sp
1138 This target provides stricter clock accuracy guarantees than
1139 time\-set\&.target
1140 (see above), but likely requires network communication and thus introduces unpredictable delays\&. Services that require clock accuracy and where network communication delays are acceptable should use this target\&. Services that require a less accurate clock, and only approximate and roughly monotonic clock behaviour should use
1141 time\-set\&.target
1142 instead\&.
1143 .sp
1144 Note that ordering a unit after
1145 time\-sync\&.target
1146 only has effect if there\*(Aqs actually a service ordered before it that delays it until clock synchronization is reached\&. Otherwise, this target might get reached before the clock is synchronized to any remote accurate reference clock\&. When using
1147 \fBsystemd-timesyncd.service\fR(8), enable
1148 \fBsystemd-time-wait-sync.service\fR(8)
1149 to delay the target; or use an equivalent service for other NTP implementations\&.
1150 .sp
1151 .it 1 an-trap
1152 .nr an-no-space-flag 1
1153 .nr an-break-flag 1
1154 .br
1155 .B Table\ \&1.\ \&Comparison
1156 .TS
1157 allbox tab(:);
1158 lB lB.
1159 T{
1160 time\-set\&.target
1161 T}:T{
1162 time\-sync\&.target
1163 T}
1164 .T&
1165 l l
1166 l l
1167 l l
1168 l l
1169 l l.
1170 T{
1171 "quick" to reach
1172 T}:T{
1173 "slow" to reach
1174 T}
1175 T{
1176 typically uses local clock sources, boot process not affected by availability of external resources
1177 T}:T{
1178 typically uses remote clock sources, inserts dependencies on remote resources into boot process
1179 T}
1180 T{
1181 reliable, because local
1182 T}:T{
1183 unreliable, because typically network involved
1184 T}
1185 T{
1186 typically guarantees an approximate and roughly monotonic clock only
1187 T}:T{
1188 typically guarantees an accurate clock
1189 T}
1190 T{
1191 implemented by systemd\-timesyncd\&.service
1192 T}:T{
1193 implemented by systemd\-time\-wait\-sync\&.service
1194 T}
1195 .TE
1196 .sp 1
1197 .RE
1198 .SS "Special Slice Units"
1199 .PP
1200 There are four
1201 "\&.slice"
1202 units which form the basis of the hierarchy for assignment of resources for services, users, and virtual machines or containers\&. See
1203 \fBsystemd.slice\fR(5)
1204 for details about slice units\&.
1205 .PP
1206 \-\&.slice
1207 .RS 4
1208 The root slice is the root of the slice hierarchy\&. It usually does not contain units directly, but may be used to set defaults for the whole tree\&.
1209 .sp
1210 Added in version 206\&.
1211 .RE
1212 .PP
1213 machine\&.slice
1214 .RS 4
1215 By default, all virtual machines and containers registered with
1216 \fBsystemd\-machined\fR
1217 are found in this slice\&. This is pulled in by
1218 systemd\-machined\&.service\&.
1219 .sp
1220 Added in version 206\&.
1221 .RE
1222 .PP
1223 capsule\&.slice
1224 .RS 4
1225 By default, all capsules encapsulated in
1226 capsule@\&.service
1227 are found in this slice\&.
1228 .sp
1229 Added in version 255\&.
1230 .RE
1231 .PP
1232 system\&.slice
1233 .RS 4
1234 By default, all system services started by
1235 \fBsystemd\fR
1236 are found in this slice\&.
1237 .sp
1238 Added in version 206\&.
1239 .RE
1240 .PP
1241 user\&.slice
1242 .RS 4
1243 By default, all user processes and services started on behalf of the user, including the per\-user systemd instance are found in this slice\&. This is pulled in by
1244 systemd\-logind\&.service\&.
1245 .sp
1246 Added in version 206\&.
1247 .RE
1248 .SH "UNITS MANAGED BY THE USER SERVICE MANAGER"
1249 .SS "Special User Units"
1250 .PP
1251 When systemd runs as a user instance, the following special units are available:
1252 .PP
1253 default\&.target
1254 .RS 4
1255 This is the main target of the user service manager, started by default when the service manager is invoked\&. Various services that compose the normal user session should be pulled into this target\&. In this regard,
1256 default\&.target
1257 is similar to
1258 multi\-user\&.target
1259 in the system instance, but it is a real unit, not an alias\&.
1260 .sp
1261 Added in version 242\&.
1262 .RE
1263 .PP
1264 capsule@\&.target
1265 .RS 4
1266 This is the main target of capsule service managers, started by default, instantiated with the capsule name\&. This may be used to define different sets of units that are started for different capsules via generic unit definitions\&. For details about capsules see
1267 \[email protected]\fR(5)\&.
1268 .sp
1269 Added in version 255\&.
1270 .RE
1271 .PP
1272 In addition, the following units are available which have definitions similar to their system counterparts:
1273 exit\&.target,
1274 shutdown\&.target,
1275 sockets\&.target,
1276 timers\&.target,
1277 paths\&.target,
1278 bluetooth\&.target,
1279 printer\&.target,
1280 smartcard\&.target,
1281 sound\&.target\&.
1282 .SS "Special Passive User Units"
1283 .PP
1284 graphical\-session\&.target
1285 .RS 4
1286 This target is active whenever any graphical session is running\&. It is used to stop user services which only apply to a graphical (X, Wayland, etc\&.) session when the session is terminated\&. Such services should have
1287 "PartOf=graphical\-session\&.target"
1288 in their [Unit] section\&. A target for a particular session (e\&. g\&.
1289 gnome\-session\&.target) starts and stops
1290 "graphical\-session\&.target"
1291 with
1292 "BindsTo=graphical\-session\&.target"\&.
1293 .sp
1294 Which services are started by a session target is determined by the
1295 "Wants="
1296 and
1297 "Requires="
1298 dependencies\&. For services that can be enabled independently, symlinks in
1299 "\&.wants/"
1300 and
1301 "\&.requires/"
1302 should be used, see
1303 \fBsystemd.unit\fR(5)\&. Those symlinks should either be shipped in packages, or should be added dynamically after installation, for example using
1304 "systemctl add\-wants", see
1305 \fBsystemctl\fR(1)\&.
1306 .PP
1307 \fBExample\ \&2.\ \&Nautilus as part of a GNOME session\fR
1308 "gnome\-session\&.target"
1309 pulls in Nautilus as top\-level service:
1310 .sp
1311 .if n \{\
1312 .RS 4
1313 .\}
1314 .nf
1315 [Unit]
1316 Description=User systemd services for GNOME graphical session
1317 Wants=nautilus\&.service
1318 BindsTo=graphical\-session\&.target
1319 .fi
1320 .if n \{\
1321 .RE
1322 .\}
1323 .sp
1324 "nautilus\&.service"
1325 gets stopped when the session stops:
1326 .sp
1327 .if n \{\
1328 .RS 4
1329 .\}
1330 .nf
1331 [Unit]
1332 Description=Render the desktop icons with Nautilus
1333 PartOf=graphical\-session\&.target
1334
1335 [Service]
1336 \&...
1337 .fi
1338 .if n \{\
1339 .RE
1340 .\}
1341
1342 Added in version 234\&.
1343 .RE
1344 .PP
1345 graphical\-session\-pre\&.target
1346 .RS 4
1347 This target contains services which set up the environment or global configuration of a graphical session, such as SSH/GPG agents (which need to export an environment variable into all desktop processes) or migration of obsolete d\-conf keys after an OS upgrade (which needs to happen before starting any process that might use them)\&. This target must be started before starting a graphical session like
1348 gnome\-session\&.target\&.
1349 .sp
1350 Added in version 234\&.
1351 .RE
1352 .PP
1353 xdg\-desktop\-autostart\&.target
1354 .RS 4
1355 The XDG specification defines a way to autostart applications using XDG desktop files\&. systemd ships
1356 \fBsystemd-xdg-autostart-generator\fR(8)
1357 for the XDG desktop files in autostart directories\&. Desktop Environments can opt\-in to use this service by adding a
1358 \fIWants=\fR
1359 dependency on
1360 xdg\-desktop\-autostart\&.target\&.
1361 .sp
1362 Added in version 246\&.
1363 .RE
1364 .SS "Special User Slice Units"
1365 .PP
1366 There are four
1367 "\&.slice"
1368 units which form the basis of the user hierarchy for assignment of resources for user applications and services\&. See
1369 \fBsystemd.slice\fR(5)
1370 for details about slice units and the documentation about
1371 \m[blue]\fBDesktop Environments\fR\m[]\&\s-2\u[4]\d\s+2
1372 for further information\&.
1373 .PP
1374 \-\&.slice
1375 .RS 4
1376 The root slice is the root of the user\*(Aqs slice hierarchy\&. It usually does not contain units directly, but may be used to set defaults for the whole tree\&.
1377 .sp
1378 Added in version 247\&.
1379 .RE
1380 .PP
1381 app\&.slice
1382 .RS 4
1383 By default, all user services and applications managed by
1384 \fBsystemd\fR
1385 are found in this slice\&. All interactively launched applications like web browsers and text editors as well as non\-critical services should be placed into this slice\&.
1386 .sp
1387 Added in version 247\&.
1388 .RE
1389 .PP
1390 session\&.slice
1391 .RS 4
1392 All essential services and applications required for the session should use this slice\&. These are services that either cannot be restarted easily or where latency issues may affect the interactivity of the system and applications\&. This includes the display server, screen readers and other services such as DBus or XDG portals\&. Such services should be configured to be part of this slice by adding
1393 \fISlice=session\&.slice\fR
1394 to their unit files\&.
1395 .sp
1396 Added in version 247\&.
1397 .RE
1398 .PP
1399 background\&.slice
1400 .RS 4
1401 All services running low\-priority background tasks should use this slice\&. This permits resources to be preferentially assigned to the other slices\&. Examples include non\-interactive tasks like file indexing or backup operations where latency is not important\&.
1402 .sp
1403 Added in version 247\&.
1404 .RE
1405 .SH "SEE ALSO"
1406 .PP
1407 \fBsystemd\fR(1), \fBsystemd.unit\fR(5), \fBsystemd.service\fR(5), \fBsystemd.socket\fR(5), \fBsystemd.target\fR(5), \fBsystemd.slice\fR(5), \fBbootup\fR(7), \fBsystemd-fstab-generator\fR(8), \[email protected]\fR(5)
1408 .SH "NOTES"
1409 .IP " 1." 4
1410 Factory Reset
1411 .RS 4
1412 \%https://systemd.io/FACTORY_RESET
1413 .RE
1414 .IP " 2." 4
1415 Running Services After the Network Is Up
1416 .RS 4
1417 \%https://systemd.io/NETWORK_ONLINE
1418 .RE
1419 .IP " 3." 4
1420 Syslog Interface
1421 .RS 4
1422 \%https://systemd.io/SYSLOG
1423 .RE
1424 .IP " 4." 4
1425 Desktop Environments
1426 .RS 4
1427 \%https://systemd.io/DESKTOP_ENVIRONMENTS
1428 .RE