Debian Codegraph @

upstream/debian-trixie/man7/systemd.special.7

raw
1 '\" t
2 .TH "SYSTEMD\&.SPECIAL" "7" "" "systemd 257.13" "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 final\&.target,
40 first\-boot\-complete\&.target,
41 getty\&.target,
42 getty\-pre\&.target,
43 graphical\&.target,
44 halt\&.target,
45 hibernate\&.target,
46 hybrid\-sleep\&.target,
47 suspend\-then\-hibernate\&.target,
48 initrd\&.target,
49 initrd\-fs\&.target,
50 initrd\-root\-device\&.target,
51 initrd\-root\-fs\&.target,
52 initrd\-usr\-fs\&.target,
53 integritysetup\-pre\&.target,
54 integritysetup\&.target,
55 kbrequest\&.target,
56 kexec\&.target,
57 local\-fs\-pre\&.target,
58 local\-fs\&.target,
59 machines\&.target,
60 multi\-user\&.target,
61 network\-online\&.target,
62 network\-pre\&.target,
63 network\&.target,
64 nss\-lookup\&.target,
65 nss\-user\-lookup\&.target,
66 paths\&.target,
67 poweroff\&.target,
68 printer\&.target,
69 reboot\&.target,
70 remote\-cryptsetup\&.target,
71 remote\-veritysetup\&.target,
72 remote\-fs\-pre\&.target,
73 remote\-fs\&.target,
74 rescue\&.target,
75 rpcbind\&.target,
76 runlevel2\&.target,
77 runlevel3\&.target,
78 runlevel4\&.target,
79 runlevel5\&.target,
80 shutdown\&.target,
81 sigpwr\&.target,
82 sleep\&.target,
83 slices\&.target,
84 smartcard\&.target,
85 sockets\&.target,
86 soft\-reboot\&.target,
87 sound\&.target,
88 ssh\-access\&.target,
89 storage\-target\-mode\&.target,
90 suspend\&.target,
91 swap\&.target,
92 sysinit\&.target,
93 system\-update\&.target,
94 system\-update\-pre\&.target,
95 time\-set\&.target,
96 time\-sync\&.target,
97 timers\&.target,
98 tpm2\&.target,
99 umount\&.target,
100 usb\-gadget\&.target,
101 \-\&.slice,
102 capsule\&.slice,
103 machine\&.slice,
104 system\&.slice,
105 user\&.slice,
106 \-\&.mount,
107 dbus\&.service,
108 dbus\&.socket,
109 display\-manager\&.service,
110 init\&.scope,
111 syslog\&.socket,
112 system\-update\-cleanup\&.service
113 .SH "DESCRIPTION"
114 .PP
115 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\&.
116 .SH "UNITS MANAGED BY THE SYSTEM SERVICE MANAGER"
117 .SS "Special System Units"
118 .PP
119 \-\&.mount
120 .RS 4
121 The root mount point, i\&.e\&. the mount unit for the
122 /
123 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\&.
124 .sp
125 Added in version 235\&.
126 .RE
127 .PP
128 basic\&.target
129 .RS 4
130 A special target unit covering basic boot\-up\&.
131 .sp
132 systemd automatically adds dependency of the type
133 \fIAfter=\fR
134 for this target unit to all services (except for those with
135 \fIDefaultDependencies=no\fR)\&.
136 .sp
137 Usually, this should pull\-in all local mount points plus
138 /var/,
139 /tmp/
140 and
141 /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\&.
142 .sp
143 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
144 \fBbootup\fR(7)
145 for details on the targets involved\&.
146 .RE
147 .PP
148 boot\-complete\&.target
149 .RS 4
150 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
151 \fIRequires=\fR
152 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
153 \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\&.
154 .sp
155 See
156 \fBsystemd-boot-check-no-failures.service\fR(8)
157 for a service that implements a generic system health check and orders itself before
158 boot\-complete\&.target\&.
159 .sp
160 See
161 \fBsystemd-bless-boot.service\fR(8)
162 for a service that propagates boot success information to the boot loader, and orders itself after
163 boot\-complete\&.target\&.
164 .sp
165 Added in version 240\&.
166 .RE
167 .PP
168 ctrl\-alt\-del\&.target
169 .RS 4
170 systemd starts this target whenever Control+Alt+Del is pressed on the console\&. Usually, this should be aliased (symlinked) to
171 reboot\&.target\&.
172 .RE
173 .PP
174 cryptsetup\&.target
175 .RS 4
176 A target that pulls in setup services for all encrypted block devices\&.
177 .RE
178 .PP
179 veritysetup\&.target
180 .RS 4
181 A target that pulls in setup services for all verity integrity protected block devices\&.
182 .sp
183 Added in version 248\&.
184 .RE
185 .PP
186 dbus\&.service
187 .RS 4
188 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\&.
189 .RE
190 .PP
191 dbus\&.socket
192 .RS 4
193 A special unit for the D\-Bus system bus socket\&. All units with
194 \fIType=dbus\fR
195 automatically gain a dependency on this unit\&.
196 .RE
197 .PP
198 default\&.target
199 .RS 4
200 The default unit systemd starts at bootup\&. Usually, this should be aliased (symlinked) to
201 multi\-user\&.target
202 or
203 graphical\&.target\&. See
204 \fBbootup\fR(7)
205 for more discussion\&.
206 .sp
207 The default unit systemd starts at bootup can be overridden with the
208 \fIsystemd\&.unit=\fR
209 kernel command line option, or more conveniently, with the short names like
210 \fIsingle\fR,
211 \fIrescue\fR,
212 \fI1\fR,
213 \fI3\fR,
214 \fI5\fR, \&...; see
215 \fBsystemd\fR(1)\&.
216 .sp
217 For typical unit files please set
218 "WantedBy="
219 to a regular target (like
220 multi\-user\&.target
221 or
222 graphical\&.target), instead of
223 default\&.target, since such a service will also be run on special boots like on system update, emergency boot\&...
224 .RE
225 .PP
226 display\-manager\&.service
227 .RS 4
228 The display manager service\&. Usually, this should be aliased (symlinked) to
229 gdm\&.service
230 or a similar display manager service\&.
231 .RE
232 .PP
233 emergency\&.target
234 .RS 4
235 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
236 \fIemergency\fR
237 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
238 rescue\&.target, which serves a similar purpose, but also starts the most basic services and mounts all file systems\&.
239 .sp
240 In many ways booting into
241 emergency\&.target
242 is similar to the effect of booting with
243 "init=/bin/sh"
244 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\&.
245 .sp
246 Note that depending on how
247 emergency\&.target
248 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
249 \fIro\fR
250 is used on the kernel command line and remain this way for
251 emergency\&.target, or the system may transition to
252 emergency\&.target
253 after the system has been partially booted and disks have already been remounted read\-write\&.
254 .RE
255 .PP
256 exit\&.target
257 .RS 4
258 A special service unit for shutting down the system or user service manager\&. It is equivalent to
259 poweroff\&.target
260 on non\-container systems, and also works in containers\&.
261 .sp
262 systemd will start this unit when it receives the
263 \fBSIGTERM\fR
264 or
265 \fBSIGINT\fR
266 signal when running as user service daemon\&.
267 .sp
268 Normally, this (indirectly) pulls in
269 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\&.
270 .sp
271 Added in version 186\&.
272 .RE
273 .PP
274 factory\-reset\&.target
275 .RS 4
276 A special target to trigger a factory reset\&.
277 .sp
278 Added in version 250\&.
279 .RE
280 .PP
281 final\&.target
282 .RS 4
283 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\&.
284 .RE
285 .PP
286 getty\&.target
287 .RS 4
288 A special target unit that pulls in statically configured local TTY
289 getty
290 instances\&.
291 .RE
292 .PP
293 graphical\&.target
294 .RS 4
295 A special target unit for setting up a graphical login screen\&. This pulls in
296 multi\-user\&.target\&.
297 .sp
298 Units that are needed for graphical logins shall add
299 \fIWants=\fR
300 dependencies for their unit to this unit (or
301 multi\-user\&.target) during installation\&. This is best configured via
302 \fIWantedBy=graphical\&.target\fR
303 in the unit\*(Aqs [Install] section\&.
304 .RE
305 .PP
306 hibernate\&.target
307 .RS 4
308 A special target unit for hibernating the system\&. This pulls in
309 sleep\&.target\&.
310 .RE
311 .PP
312 hybrid\-sleep\&.target
313 .RS 4
314 A special target unit for hibernating and suspending the system at the same time\&. This pulls in
315 sleep\&.target\&.
316 .sp
317 Added in version 196\&.
318 .RE
319 .PP
320 suspend\-then\-hibernate\&.target
321 .RS 4
322 A special target unit for suspending the system for a period of time, waking it and putting it into hibernate\&. This pulls in
323 sleep\&.target\&.
324 .sp
325 Added in version 239\&.
326 .RE
327 .PP
328 halt\&.target
329 .RS 4
330 A special target unit for shutting down and halting the system\&. Note that this target is distinct from
331 poweroff\&.target
332 in that it generally really just halts the system rather than powering it down\&.
333 .sp
334 Applications wanting to halt the system should not start this unit directly, but should instead execute
335 \fBsystemctl halt\fR
336 (possibly with the
337 \fB\-\-no\-block\fR
338 option) or call
339 \fBsystemd\fR(1)\*(Aqs
340 \fBorg\&.freedesktop\&.systemd1\&.Manager\&.Halt\fR
341 D\-Bus method directly\&.
342 .RE
343 .PP
344 init\&.scope
345 .RS 4
346 This scope unit is where the system and service manager (PID 1) itself resides\&. It is active as long as the system is running\&.
347 .sp
348 Added in version 235\&.
349 .RE
350 .PP
351 initrd\&.target
352 .RS 4
353 This is the default target in the initrd, similar to
354 default\&.target
355 in the main system\&. It is used to mount the real root and transition to it\&. See
356 \fBbootup\fR(7)
357 for more discussion\&.
358 .sp
359 Added in version 245\&.
360 .RE
361 .PP
362 initrd\-fs\&.target
363 .RS 4
364 \fBsystemd-fstab-generator\fR(8)
365 automatically adds dependencies of type
366 \fIBefore=\fR
367 to
368 sysroot\-usr\&.mount
369 and all mount points found in
370 /etc/fstab
371 that have the
372 \fBx\-initrd\&.mount\fR
373 mount option set and do not have the
374 \fBnoauto\fR
375 mount option set\&. It is also indirectly ordered after
376 sysroot\&.mount\&. Thus, once this target is reached the
377 /sysroot/
378 hierarchy is fully set up, in preparation for the transition to the host OS\&.
379 .sp
380 Added in version 199\&.
381 .RE
382 .PP
383 initrd\-root\-device\&.target
384 .RS 4
385 A special initrd target unit that is reached when the root filesystem device is available, but before it has been mounted\&.
386 \fBsystemd-fstab-generator\fR(8)
387 and
388 \fBsystemd-gpt-auto-generator\fR(8)
389 automatically set up the appropriate dependencies to make this happen\&.
390 .sp
391 Added in version 230\&.
392 .RE
393 .PP
394 initrd\-root\-fs\&.target
395 .RS 4
396 \fBsystemd-fstab-generator\fR(8)
397 automatically adds dependencies of type
398 \fIBefore=\fR
399 to the
400 sysroot\&.mount
401 unit, which is generated from the kernel command line\*(Aqs
402 \fIroot=\fR
403 setting (or equivalent)\&.
404 .sp
405 Added in version 199\&.
406 .RE
407 .PP
408 initrd\-usr\-fs\&.target
409 .RS 4
410 \fBsystemd-fstab-generator\fR(8)
411 automatically adds dependencies of type
412 \fIBefore=\fR
413 to the
414 sysusr\-usr\&.mount
415 unit, which is generated from the kernel command line\*(Aqs
416 \fIusr=\fR
417 switch\&. Services may order themselves after this target unit in order to run once the
418 /sysusr/
419 hierarchy becomes available, on systems that come up initially without a root file system, but with an initialized
420 /usr/
421 and need to access that before setting up the root file system to ultimately switch to\&. On systems where
422 \fIusr=\fR
423 is not used this target is ordered after
424 sysroot\&.mount
425 and thus mostly equivalent to
426 initrd\-root\-fs\&.target\&. In effect on any system once this target is reached the file system backing
427 /usr/
428 is mounted, though possibly at two different locations, either below the
429 /sysusr/
430 or the
431 /sysroot/
432 hierarchies\&.
433 .sp
434 Added in version 249\&.
435 .RE
436 .PP
437 kbrequest\&.target
438 .RS 4
439 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\&.
440 .RE
441 .PP
442 kexec\&.target
443 .RS 4
444 A special target unit for shutting down and rebooting the system via kexec\&.
445 .sp
446 Applications wanting to reboot the system should not start this unit directly, but should instead execute
447 \fBsystemctl kexec\fR
448 (possibly with the
449 \fB\-\-no\-block\fR
450 option) or call
451 \fBsystemd-logind\fR(8)\*(Aqs
452 \fBorg\&.freedesktop\&.login1\&.Manager\&.RebootWithFlags()\fR
453 D\-Bus method directly\&.
454 .sp
455 See
456 \fBsystemd-kexec.service\fR(8)
457 for further details of the operation this target pulls in\&.
458 .RE
459 .PP
460 local\-fs\&.target
461 .RS 4
462 \fBsystemd-fstab-generator\fR(8)
463 automatically adds dependencies of type
464 \fIBefore=\fR
465 to all mount units that refer to local mount points for this target unit\&. In addition, it adds dependencies of type
466 \fIWants=\fR
467 to this target unit for those mounts listed in
468 /etc/fstab
469 that have the
470 \fBauto\fR
471 mount option set\&.
472 .RE
473 .PP
474 machines\&.target
475 .RS 4
476 A standard target unit for starting all the containers and other virtual machines\&. See
477 systemd\-nspawn@\&.service
478 for an example\&.
479 .sp
480 Added in version 233\&.
481 .RE
482 .PP
483 multi\-user\&.target
484 .RS 4
485 A special target unit for setting up a multi\-user system (non\-graphical)\&. This is pulled in by
486 graphical\&.target\&.
487 .sp
488 Units that are needed for a multi\-user system shall add
489 \fIWants=\fR
490 dependencies for their unit to this unit during installation\&. This is best configured via
491 \fIWantedBy=multi\-user\&.target\fR
492 in the unit\*(Aqs [Install] section\&.
493 .RE
494 .PP
495 network\-online\&.target
496 .RS 4
497 Units that strictly require a configured network connection should pull in
498 network\-online\&.target
499 (via a
500 \fIWants=\fR
501 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\&.
502 .sp
503 Note the distinction between this unit and
504 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,
505 network\&.target
506 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,
507 network\&.target
508 is part of the boot of most systems, while
509 network\-online\&.target
510 is not, except when at least one unit requires it\&. Also see
511 \m[blue]\fBRunning Services After the Network Is Up\fR\m[]\&\s-2\u[1]\d\s+2
512 for more information\&.
513 .sp
514 All mount units for remote network file systems automatically pull in this unit, and order themselves after it\&. Note that networking daemons that simply
515 \fIprovide\fR
516 functionality to other hosts (as opposed to
517 \fIconsume\fR
518 functionality of other hosts) generally do not need to pull this in\&.
519 .sp
520 systemd automatically adds dependencies of type
521 \fIWants=\fR
522 and
523 \fIAfter=\fR
524 for this target unit to all SysV init script service units with an LSB header referring to the
525 "$network"
526 facility\&.
527 .sp
528 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\&.
529 .sp
530 Added in version 200\&.
531 .RE
532 .PP
533 paths\&.target
534 .RS 4
535 A special target unit that sets up all path units (see
536 \fBsystemd.path\fR(5)
537 for details) that shall be active after boot\&.
538 .sp
539 It is recommended that path units installed by applications get pulled in via
540 \fIWants=\fR
541 dependencies from this unit\&. This is best configured via a
542 \fIWantedBy=paths\&.target\fR
543 in the path unit\*(Aqs [Install] section\&.
544 .sp
545 Added in version 199\&.
546 .RE
547 .PP
548 poweroff\&.target
549 .RS 4
550 A special target unit for shutting down and powering off the system\&.
551 .sp
552 Applications wanting to power off the system should not start this unit directly, but should instead execute
553 \fBsystemctl poweroff\fR
554 (possibly with the
555 \fB\-\-no\-block\fR
556 option) or call
557 \fBsystemd-logind\fR(8)\*(Aqs
558 \fBorg\&.freedesktop\&.login1\&.Manager\&.PowerOff\fR
559 D\-Bus method directly\&.
560 .sp
561 runlevel0\&.target
562 is an alias for this target unit, for compatibility with SysV\&.
563 .RE
564 .PP
565 reboot\&.target
566 .RS 4
567 A special target unit for shutting down and rebooting the system\&.
568 .sp
569 Applications wanting to reboot the system should not start this unit directly, but should instead execute
570 \fBsystemctl reboot\fR
571 (possibly with the
572 \fB\-\-no\-block\fR
573 option) or call
574 \fBsystemd-logind\fR(8)\*(Aqs
575 \fBorg\&.freedesktop\&.login1\&.Manager\&.Reboot()\fR
576 D\-Bus method directly\&.
577 .sp
578 See
579 \fBsystemd-reboot.service\fR(8)
580 for further details of the operation this target pulls in\&.
581 .sp
582 runlevel6\&.target
583 is an alias for this target unit, for compatibility with SysV\&.
584 .RE
585 .PP
586 remote\-cryptsetup\&.target
587 .RS 4
588 Similar to
589 cryptsetup\&.target, but for encrypted devices which are accessed over the network\&. It is used for
590 \fBcrypttab\fR(5)
591 entries marked with
592 \fB_netdev\fR\&.
593 .sp
594 Added in version 235\&.
595 .RE
596 .PP
597 remote\-veritysetup\&.target
598 .RS 4
599 Similar to
600 veritysetup\&.target, but for verity integrity protected devices which are accessed over the network\&. It is used for
601 \fBveritytab\fR(5)
602 entries marked with
603 \fB_netdev\fR\&.
604 .sp
605 Added in version 248\&.
606 .RE
607 .PP
608 remote\-fs\&.target
609 .RS 4
610 Similar to
611 local\-fs\&.target, but for remote mount points\&.
612 .sp
613 systemd automatically adds dependencies of type
614 \fIAfter=\fR
615 for this target unit to all SysV init script service units with an LSB header referring to the
616 "$remote_fs"
617 facility\&.
618 .RE
619 .PP
620 rescue\&.target
621 .RS 4
622 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
623 emergency\&.target, which is much more reduced and does not provide the file systems or most basic services\&. Compare with
624 multi\-user\&.target, this target could be seen as
625 single\-user\&.target\&.
626 .sp
627 runlevel1\&.target
628 is an alias for this target unit, for compatibility with SysV\&.
629 .sp
630 Use the
631 "systemd\&.unit=rescue\&.target"
632 kernel command line option to boot into this mode\&. A short alias for this kernel command line option is
633 "1", for compatibility with SysV\&.
634 .RE
635 .PP
636 runlevel2\&.target, runlevel3\&.target, runlevel4\&.target, runlevel5\&.target
637 .RS 4
638 These are targets that are called whenever the SysV compatibility code asks for runlevel 2, 3, 4, 5, respectively\&. It is a good idea to make this an alias for (i\&.e\&. symlink to)
639 graphical\&.target
640 (for runlevel 5) or
641 multi\-user\&.target
642 (the others)\&.
643 .RE
644 .PP
645 shutdown\&.target
646 .RS 4
647 A special target unit that terminates the services on system shutdown\&.
648 .sp
649 Services that shall be terminated on system shutdown shall add
650 \fIConflicts=\fR
651 and
652 \fIBefore=\fR
653 dependencies to this unit for their service unit, which is implicitly done when
654 \fIDefaultDependencies=yes\fR
655 is set (the default)\&.
656 .RE
657 .PP
658 sigpwr\&.target
659 .RS 4
660 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\&.
661 .RE
662 .PP
663 sleep\&.target
664 .RS 4
665 A special target unit that is pulled in by
666 suspend\&.target,
667 hibernate\&.target
668 and
669 hybrid\-sleep\&.target
670 and may be used to hook units into the sleep state logic\&.
671 .RE
672 .PP
673 slices\&.target
674 .RS 4
675 A special target unit that sets up all slice units (see
676 \fBsystemd.slice\fR(5)
677 for details) that shall always be active after boot\&. By default, the generic
678 system\&.slice
679 slice unit as well as the root slice unit
680 \-\&.slice
681 are pulled in and ordered before this unit (see below)\&.
682 .sp
683 Adding slice units to
684 slices\&.target
685 is generally not necessary\&. Instead, when some unit that uses
686 \fISlice=\fR
687 is started, the specified slice will be started automatically\&. Adding
688 \fIWantedBy=slices\&.target\fR
689 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\&.
690 .sp
691 Added in version 229\&.
692 .RE
693 .PP
694 sockets\&.target
695 .RS 4
696 A special target unit that sets up all socket units (see
697 \fBsystemd.socket\fR(5)
698 for details) that shall be active after boot\&.
699 .sp
700 Services that can be socket\-activated shall add
701 \fIWants=\fR
702 dependencies to this unit for their socket unit during installation\&. This is best configured via a
703 \fIWantedBy=sockets\&.target\fR
704 in the socket unit\*(Aqs [Install] section\&.
705 .RE
706 .PP
707 soft\-reboot\&.target
708 .RS 4
709 A special target unit for shutting down and rebooting the userspace of the system (leaving the kernel running)\&.
710 .sp
711 Applications wanting to reboot the system should not start this unit directly, but should instead execute
712 \fBsystemctl soft\-reboot\fR
713 (possibly with the
714 \fB\-\-no\-block\fR
715 option) or call
716 \fBsystemd-logind\fR(8)\*(Aqs
717 \fBorg\&.freedesktop\&.login1\&.Manager\&.RebootWithFlags()\fR
718 D\-Bus method directly\&.
719 .sp
720 See
721 \fBsystemd-soft-reboot.service\fR(8)
722 for further details of the operation this target pulls in\&.
723 .sp
724 Added in version 254\&.
725 .RE
726 .PP
727 storage\-target\-mode\&.target
728 .RS 4
729 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
730 \fBsystemd-storagetm.service\fR(8)
731 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\&.
732 .sp
733 Added in version 255\&.
734 .RE
735 .PP
736 suspend\&.target
737 .RS 4
738 A special target unit for suspending the system\&. This pulls in
739 sleep\&.target\&.
740 .RE
741 .PP
742 swap\&.target
743 .RS 4
744 Similar to
745 local\-fs\&.target, but for swap partitions and swap files\&.
746 .RE
747 .PP
748 sysinit\&.target
749 .RS 4
750 systemd automatically adds dependencies of the types
751 \fIRequires=\fR
752 and
753 \fIAfter=\fR
754 for this target unit to all services (except for those with
755 \fIDefaultDependencies=no\fR)\&.
756 .sp
757 This target pulls in the services required for system initialization\&. System services pulled in by this target should declare
758 \fIDefaultDependencies=no\fR
759 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
760 \fBbootup\fR(7)\&.
761 .RE
762 .PP
763 syslog\&.socket
764 .RS 4
765 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
766 \m[blue]\fBSyslog Interface\fR\m[]\&\s-2\u[2]\d\s+2
767 document\&.
768 .RE
769 .PP
770 system\-update\&.target, system\-update\-pre\&.target, system\-update\-cleanup\&.service
771 .RS 4
772 A special target unit that is used for offline system updates\&.
773 \fBsystemd-system-update-generator\fR(8)
774 will redirect the boot process to this target if
775 /system\-update
776 or
777 /etc/system\-update
778 exists\&. For more information see
779 \fBsystemd.offline-updates\fR(7)\&.
780 .sp
781 Updates should happen before the
782 system\-update\&.target
783 is reached, and the services which implement them should cause the machine to reboot\&. The main units executing the update should order themselves after
784 system\-update\-pre\&.target
785 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
786 /system\-update
787 or
788 /etc/system\-update
789 still exists after
790 system\-update\&.target
791 is reached,
792 system\-update\-cleanup\&.service
793 will remove the symlinks and reboot the machine\&.
794 .sp
795 Added in version 186\&.
796 .RE
797 .PP
798 timers\&.target
799 .RS 4
800 A special target unit that sets up all timer units (see
801 \fBsystemd.timer\fR(5)
802 for details) that shall be active after boot\&.
803 .sp
804 It is recommended that timer units installed by applications get pulled in via
805 \fIWants=\fR
806 dependencies from this unit\&. This is best configured via
807 \fIWantedBy=timers\&.target\fR
808 in the timer unit\*(Aqs [Install] section\&.
809 .sp
810 Added in version 199\&.
811 .RE
812 .PP
813 umount\&.target
814 .RS 4
815 A special target unit that unmounts all mount and automount points on system shutdown\&.
816 .sp
817 Mounts that shall be unmounted on system shutdown shall add Conflicts dependencies to this unit for their mount unit, which is implicitly done when
818 \fIDefaultDependencies=yes\fR
819 is set (the default)\&.
820 .RE
821 .SS "Special System Units for Devices"
822 .PP
823 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\&.
824 .PP
825 bluetooth\&.target
826 .RS 4
827 This target is started automatically as soon as a Bluetooth controller is plugged in or becomes available at boot\&.
828 .sp
829 This may be used to pull in Bluetooth management daemons dynamically when Bluetooth hardware is found\&.
830 .RE
831 .PP
832 printer\&.target
833 .RS 4
834 This target is started automatically as soon as a printer is plugged in or becomes available at boot\&.
835 .sp
836 This may be used to pull in printer management daemons dynamically when printer hardware is found\&.
837 .RE
838 .PP
839 smartcard\&.target
840 .RS 4
841 This target is started automatically as soon as a smartcard controller is plugged in or becomes available at boot\&.
842 .sp
843 This may be used to pull in smartcard management daemons dynamically when smartcard hardware is found\&.
844 .RE
845 .PP
846 sound\&.target
847 .RS 4
848 This target is started automatically as soon as a sound card is plugged in or becomes available at boot\&.
849 .sp
850 This may be used to pull in audio management daemons dynamically when audio hardware is found\&.
851 .RE
852 .PP
853 usb\-gadget\&.target
854 .RS 4
855 This target is started automatically as soon as a USB Device Controller becomes available at boot\&.
856 .sp
857 This may be used to pull in usb gadget dynamically when UDC hardware is found\&.
858 .sp
859 Added in version 242\&.
860 .RE
861 .PP
862 tpm2\&.target
863 .RS 4
864 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
865 \fBsystemd-tpm2-generator\fR(8)
866 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
867 \fBsystemd-udevd.service\fR(8)
868 discovers a TPM2 device\&. The target unit is ordered after the
869 /dev/tpmrm0
870 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\&.
871 .sp
872 Added in version 256\&.
873 .RE
874 .SS "Special Passive System Units"
875 .PP
876 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
877 \fIpassive\fR
878 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
879 \fIWants=\fR
880 type dependency)\&.
881 .PP
882 Note that these passive units cannot be started manually, i\&.e\&.
883 "systemctl start time\-sync\&.target"
884 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\&.
885 .PP
886 blockdev@\&.target
887 .RS 4
888 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
889 \[email protected]\fR(5)/
890 \[email protected]\fR(8)) that allocate and manage a virtual block device\&. Storage services are ordered before an instance of
891 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
892 blockdev@\&.target
893 instance should be pulled in via a
894 \fBWants=\fR
895 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\&.
896 blockdev@dev\-mapper\-foobar\&.target
897 for the storage device
898 /dev/mapper/foobar\&.
899 .sp
900 Added in version 245\&.
901 .RE
902 .PP
903 cryptsetup\-pre\&.target
904 .RS 4
905 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\&.
906 .sp
907 Added in version 215\&.
908 .RE
909 .PP
910 veritysetup\-pre\&.target
911 .RS 4
912 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\&.
913 .sp
914 Added in version 248\&.
915 .RE
916 .PP
917 first\-boot\-complete\&.target
918 .RS 4
919 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
920 \fBmachine-id\fR(5)
921 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
922 \fIConditionFirstBoot=yes\fR\&.
923 .sp
924 Added in version 247\&.
925 .RE
926 .PP
927 getty\-pre\&.target
928 .RS 4
929 A special passive target unit\&. Users of this target are expected to pull it in the boot transaction via a dependency (e\&.g\&.
930 \fIWants=\fR)\&. Order your unit before this unit if you want to make use of the console just before
931 getty
932 is started\&.
933 .sp
934 Added in version 235\&.
935 .RE
936 .PP
937 local\-fs\-pre\&.target
938 .RS 4
939 This target unit is automatically ordered before all local mount points marked with
940 \fBauto\fR
941 (see above)\&. It can be used to execute certain units before all local mounts\&.
942 .RE
943 .PP
944 network\&.target
945 .RS 4
946 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:
947 .sp
948 .RS 4
949 .ie n \{\
950 \h'-04'\(bu\h'+03'\c
951 .\}
952 .el \{\
953 .sp -1
954 .IP \(bu 2.3
955 .\}
956 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
957 network\&.target
958 is reached\&.
959 .RE
960 .sp
961 .RS 4
962 .ie n \{\
963 \h'-04'\(bu\h'+03'\c
964 .\}
965 .el \{\
966 .sp -1
967 .IP \(bu 2.3
968 .\}
969 At shutdown, a unit that is ordered after
970 network\&.target
971 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
972 \m[blue]\fBRunning Services After the Network Is Up\fR\m[]\&\s-2\u[1]\d\s+2
973 for more information\&.
974 .RE
975 .sp
976 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
977 network\-online\&.target
978 as described above\&.
979 .RE
980 .PP
981 network\-pre\&.target
982 .RS 4
983 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
984 \m[blue]\fBRunning Services After the Network Is Up\fR\m[]\&\s-2\u[1]\d\s+2
985 for more information\&.
986 .sp
987 Added in version 214\&.
988 .RE
989 .PP
990 nss\-lookup\&.target
991 .RS 4
992 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
993 nss\-user\-lookup\&.target
994 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
995 \fIAfter=\fR
996 for this target unit to all SysV init script service units with an LSB header referring to the
997 "$named"
998 facility\&.
999 .RE
1000 .PP
1001 nss\-user\-lookup\&.target
1002 .RS 4
1003 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
1004 nss\-lookup\&.target
1005 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\&.
1006 .RE
1007 .PP
1008 remote\-fs\-pre\&.target
1009 .RS 4
1010 This target unit is automatically ordered before all mount point units (see above) and cryptsetup/veritysetup devices marked with the
1011 \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
1012 \fIWants=\fR
1013 type dependency\&. If the unit wants to be pulled in by the first remote mount showing up, it should use
1014 network\-online\&.target
1015 (see above)\&.
1016 .RE
1017 .PP
1018 rpcbind\&.target
1019 .RS 4
1020 The portmapper/rpcbind pulls in this target and orders itself before it, to indicate its availability\&. systemd automatically adds dependencies of type
1021 \fIAfter=\fR
1022 for this target unit to all SysV init script service units with an LSB header referring to the
1023 "$portmap"
1024 facility\&.
1025 .RE
1026 .PP
1027 ssh\-access\&.target
1028 .RS 4
1029 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
1030 \fInot\fR
1031 involve this target unit), regardless of the protocol choices, i\&.e\&. regardless if IPv4, IPv6 or
1032 \fBAF_VSOCK\fR
1033 is used\&.
1034 .sp
1035 Added in version 256\&.
1036 .RE
1037 .PP
1038 time\-set\&.target
1039 .RS 4
1040 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\&.
1041 .sp
1042 This target does not provide the accuracy guarantees of
1043 time\-sync\&.target
1044 (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\&.
1045 .sp
1046 The service manager automatically adds dependencies of type
1047 \fIAfter=\fR
1048 for this target unit to all timer units with at least one
1049 \fIOnCalendar=\fR
1050 directive\&.
1051 .sp
1052 The
1053 \fBsystemd-timesyncd.service\fR(8)
1054 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\&.
1055 .sp
1056 Note that ordering a unit after
1057 time\-set\&.target
1058 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
1059 \fBsystemd-timesyncd.service\fR(8), or an alternative NTP implementation to delay the target\&.
1060 .sp
1061 Added in version 242\&.
1062 .RE
1063 .PP
1064 time\-sync\&.target
1065 .RS 4
1066 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\&.
1067 .sp
1068 The service manager automatically adds dependencies of type
1069 \fIAfter=\fR
1070 for this target unit to all SysV init script service units with an LSB header referring to the
1071 "$time"
1072 facility, as well to all timer units with at least one
1073 \fIOnCalendar=\fR
1074 directive\&.
1075 .sp
1076 This target provides stricter clock accuracy guarantees than
1077 time\-set\&.target
1078 (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
1079 time\-set\&.target
1080 instead\&.
1081 .sp
1082 Note that ordering a unit after
1083 time\-sync\&.target
1084 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
1085 \fBsystemd-timesyncd.service\fR(8), enable
1086 \fBsystemd-time-wait-sync.service\fR(8)
1087 to delay the target; or use an equivalent service for other NTP implementations\&.
1088 .sp
1089 .it 1 an-trap
1090 .nr an-no-space-flag 1
1091 .nr an-break-flag 1
1092 .br
1093 .B Table\ \&1.\ \&Comparison
1094 .TS
1095 allbox tab(:);
1096 lB lB.
1097 T{
1098 time\-set\&.target
1099 T}:T{
1100 time\-sync\&.target
1101 T}
1102 .T&
1103 l l
1104 l l
1105 l l
1106 l l
1107 l l.
1108 T{
1109 "quick" to reach
1110 T}:T{
1111 "slow" to reach
1112 T}
1113 T{
1114 typically uses local clock sources, boot process not affected by availability of external resources
1115 T}:T{
1116 typically uses remote clock sources, inserts dependencies on remote resources into boot process
1117 T}
1118 T{
1119 reliable, because local
1120 T}:T{
1121 unreliable, because typically network involved
1122 T}
1123 T{
1124 typically guarantees an approximate and roughly monotonic clock only
1125 T}:T{
1126 typically guarantees an accurate clock
1127 T}
1128 T{
1129 implemented by systemd\-timesyncd\&.service
1130 T}:T{
1131 implemented by systemd\-time\-wait\-sync\&.service
1132 T}
1133 .TE
1134 .sp 1
1135 .RE
1136 .SS "Special Slice Units"
1137 .PP
1138 There are four
1139 "\&.slice"
1140 units which form the basis of the hierarchy for assignment of resources for services, users, and virtual machines or containers\&. See
1141 \fBsystemd.slice\fR(5)
1142 for details about slice units\&.
1143 .PP
1144 \-\&.slice
1145 .RS 4
1146 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\&.
1147 .sp
1148 Added in version 206\&.
1149 .RE
1150 .PP
1151 machine\&.slice
1152 .RS 4
1153 By default, all virtual machines and containers registered with
1154 \fBsystemd\-machined\fR
1155 are found in this slice\&. This is pulled in by
1156 systemd\-machined\&.service\&.
1157 .sp
1158 Added in version 206\&.
1159 .RE
1160 .PP
1161 capsule\&.slice
1162 .RS 4
1163 By default, all capsules encapsulated in
1164 capsule@\&.service
1165 are found in this slice\&.
1166 .sp
1167 Added in version 255\&.
1168 .RE
1169 .PP
1170 system\&.slice
1171 .RS 4
1172 By default, all system services started by
1173 \fBsystemd\fR
1174 are found in this slice\&.
1175 .sp
1176 Added in version 206\&.
1177 .RE
1178 .PP
1179 user\&.slice
1180 .RS 4
1181 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
1182 systemd\-logind\&.service\&.
1183 .sp
1184 Added in version 206\&.
1185 .RE
1186 .SH "UNITS MANAGED BY THE USER SERVICE MANAGER"
1187 .SS "Special User Units"
1188 .PP
1189 When systemd runs as a user instance, the following special units are available:
1190 .PP
1191 default\&.target
1192 .RS 4
1193 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,
1194 default\&.target
1195 is similar to
1196 multi\-user\&.target
1197 in the system instance, but it is a real unit, not an alias\&.
1198 .sp
1199 Added in version 242\&.
1200 .RE
1201 .PP
1202 capsule@\&.target
1203 .RS 4
1204 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
1205 \[email protected]\fR(5)\&.
1206 .sp
1207 Added in version 255\&.
1208 .RE
1209 .PP
1210 In addition, the following units are available which have definitions similar to their system counterparts:
1211 exit\&.target,
1212 shutdown\&.target,
1213 sockets\&.target,
1214 timers\&.target,
1215 paths\&.target,
1216 bluetooth\&.target,
1217 printer\&.target,
1218 smartcard\&.target,
1219 sound\&.target\&.
1220 .SS "Special Passive User Units"
1221 .PP
1222 graphical\-session\&.target
1223 .RS 4
1224 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
1225 "PartOf=graphical\-session\&.target"
1226 in their [Unit] section\&. A target for a particular session (e\&. g\&.
1227 gnome\-session\&.target) starts and stops
1228 "graphical\-session\&.target"
1229 with
1230 "BindsTo=graphical\-session\&.target"\&.
1231 .sp
1232 Which services are started by a session target is determined by the
1233 "Wants="
1234 and
1235 "Requires="
1236 dependencies\&. For services that can be enabled independently, symlinks in
1237 "\&.wants/"
1238 and
1239 "\&.requires/"
1240 should be used, see
1241 \fBsystemd.unit\fR(5)\&. Those symlinks should either be shipped in packages, or should be added dynamically after installation, for example using
1242 "systemctl add\-wants", see
1243 \fBsystemctl\fR(1)\&.
1244 .PP
1245 \fBExample\ \&1.\ \&Nautilus as part of a GNOME session\fR
1246 "gnome\-session\&.target"
1247 pulls in Nautilus as top\-level service:
1248 .sp
1249 .if n \{\
1250 .RS 4
1251 .\}
1252 .nf
1253 [Unit]
1254 Description=User systemd services for GNOME graphical session
1255 Wants=nautilus\&.service
1256 BindsTo=graphical\-session\&.target
1257 .fi
1258 .if n \{\
1259 .RE
1260 .\}
1261 .sp
1262 "nautilus\&.service"
1263 gets stopped when the session stops:
1264 .sp
1265 .if n \{\
1266 .RS 4
1267 .\}
1268 .nf
1269 [Unit]
1270 Description=Render the desktop icons with Nautilus
1271 PartOf=graphical\-session\&.target
1272
1273 [Service]
1274 \&...
1275 .fi
1276 .if n \{\
1277 .RE
1278 .\}
1279
1280 Added in version 234\&.
1281 .RE
1282 .PP
1283 graphical\-session\-pre\&.target
1284 .RS 4
1285 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
1286 gnome\-session\&.target\&.
1287 .sp
1288 Added in version 234\&.
1289 .RE
1290 .PP
1291 xdg\-desktop\-autostart\&.target
1292 .RS 4
1293 The XDG specification defines a way to autostart applications using XDG desktop files\&. systemd ships
1294 \fBsystemd-xdg-autostart-generator\fR(8)
1295 for the XDG desktop files in autostart directories\&. Desktop Environments can opt\-in to use this service by adding a
1296 \fIWants=\fR
1297 dependency on
1298 xdg\-desktop\-autostart\&.target\&.
1299 .sp
1300 Added in version 246\&.
1301 .RE
1302 .SS "Special User Slice Units"
1303 .PP
1304 There are four
1305 "\&.slice"
1306 units which form the basis of the user hierarchy for assignment of resources for user applications and services\&. See
1307 \fBsystemd.slice\fR(5)
1308 for details about slice units and the documentation about
1309 \m[blue]\fBDesktop Environments\fR\m[]\&\s-2\u[3]\d\s+2
1310 for further information\&.
1311 .PP
1312 \-\&.slice
1313 .RS 4
1314 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\&.
1315 .sp
1316 Added in version 247\&.
1317 .RE
1318 .PP
1319 app\&.slice
1320 .RS 4
1321 By default, all user services and applications managed by
1322 \fBsystemd\fR
1323 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\&.
1324 .sp
1325 Added in version 247\&.
1326 .RE
1327 .PP
1328 session\&.slice
1329 .RS 4
1330 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
1331 \fISlice=session\&.slice\fR
1332 to their unit files\&.
1333 .sp
1334 Added in version 247\&.
1335 .RE
1336 .PP
1337 background\&.slice
1338 .RS 4
1339 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\&.
1340 .sp
1341 Added in version 247\&.
1342 .RE
1343 .SH "SEE ALSO"
1344 .PP
1345 \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)
1346 .SH "NOTES"
1347 .IP " 1." 4
1348 Running Services After the Network Is Up
1349 .RS 4
1350 \%https://systemd.io/NETWORK_ONLINE
1351 .RE
1352 .IP " 2." 4
1353 Syslog Interface
1354 .RS 4
1355 \%https://systemd.io/SYSLOG
1356 .RE
1357 .IP " 3." 4
1358 Desktop Environments
1359 .RS 4
1360 \%https://systemd.io/DESKTOP_ENVIRONMENTS
1361 .RE