1 <?xml version='1.0'?> <!--*-nxml-*-->
2 <!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
6 This file is part of systemd.
8 Copyright 2010 Lennart Poettering
10 systemd is free software; you can redistribute it and/or modify it
11 under the terms of the GNU Lesser General Public License as published by
12 the Free Software Foundation; either version 2.1 of the License, or
13 (at your option) any later version.
15 systemd is distributed in the hope that it will be useful, but
16 WITHOUT ANY WARRANTY; without even the implied warranty of
17 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
18 Lesser General Public License for more details.
20 You should have received a copy of the GNU Lesser General Public License
21 along with systemd; If not, see <http://www.gnu.org/licenses/>.
24 <refentry id="systemd.special">
27 <title>systemd.special</title>
28 <productname>systemd</productname>
32 <contrib>Developer</contrib>
33 <firstname>Lennart</firstname>
34 <surname>Poettering</surname>
35 <email>lennart@poettering.net</email>
41 <refentrytitle>systemd.special</refentrytitle>
42 <manvolnum>7</manvolnum>
46 <refname>systemd.special</refname>
47 <refpurpose>Special systemd units</refpurpose>
51 <para><filename>basic.target</filename>,
52 <filename>bluetooth.target</filename>,
53 <filename>ctrl-alt-del.target</filename>,
54 <filename>cryptsetup.target</filename>,
55 <filename>dbus.service</filename>,
56 <filename>dbus.socket</filename>,
57 <filename>default.target</filename>,
58 <filename>display-manager.service</filename>,
59 <filename>emergency.target</filename>,
60 <filename>exit.target</filename>,
61 <filename>final.target</filename>,
62 <filename>getty.target</filename>,
63 <filename>graphical.target</filename>,
64 <filename>halt.target</filename>,
65 <filename>hibernate.target</filename>,
66 <filename>hybrid-sleep.target</filename>,
67 <filename>initrd-fs.target</filename>,
68 <filename>kbrequest.target</filename>,
69 <filename>kexec.target</filename>,
70 <filename>local-fs.target</filename>,
71 <filename>local-fs-pre.target</filename>,
72 <filename>multi-user.target</filename>,
73 <filename>network.target</filename>,
74 <filename>network-online.target</filename>,
75 <filename>network-pre.target</filename>,
76 <filename>nss-lookup.target</filename>,
77 <filename>nss-user-lookup.target</filename>,
78 <filename>paths.target</filename>,
79 <filename>poweroff.target</filename>,
80 <filename>printer.target</filename>,
81 <filename>reboot.target</filename>,
82 <filename>remote-fs.target</filename>,
83 <filename>remote-fs-pre.target</filename>,
84 <filename>rescue.target</filename>,
85 <filename>initrd-root-fs.target</filename>,
86 <filename>rpcbind.target</filename>,
87 <filename>runlevel2.target</filename>,
88 <filename>runlevel3.target</filename>,
89 <filename>runlevel4.target</filename>,
90 <filename>runlevel5.target</filename>,
91 <filename>shutdown.target</filename>,
92 <filename>sigpwr.target</filename>,
93 <filename>sleep.target</filename>,
94 <filename>smartcard.target</filename>,
95 <filename>sockets.target</filename>,
96 <filename>sound.target</filename>,
97 <filename>suspend.target</filename>,
98 <filename>swap.target</filename>,
99 <filename>sysinit.target</filename>,
100 <filename>syslog.socket</filename>,
101 <filename>system-update.target</filename>,
102 <filename>time-sync.target</filename>,
103 <filename>timers.target</filename>,
104 <filename>umount.target</filename>,
105 <filename>-.slice</filename>,
106 <filename>system.slice</filename>,
107 <filename>user.slice</filename>,
108 <filename>machine.slice</filename></para>
112 <title>Description</title>
114 <para>A few units are treated specially by
115 systemd. They have special internal semantics and
116 cannot be renamed.</para>
120 <title>Special System Units</title>
124 <term><filename>basic.target</filename></term>
126 <para>A special target unit
127 covering basic boot-up.</para>
128 <para>systemd automatically
129 adds dependencies of the types
130 <varname>Requires=</varname>
131 and <varname>After=</varname>
132 for this target unit to all
133 services (except for those
135 <varname>DefaultDependencies=no</varname>).</para>
137 <para>Usually this should
138 pull-in all mount points, swap
139 devices, sockets, timers, and
140 path units and other basic
141 initialization necessary for
147 <term><filename>ctrl-alt-del.target</filename></term>
149 <para>systemd starts this
151 Control+Alt+Del is pressed on
152 the console. Usually this
153 should be aliased (symlinked)
155 <filename>reboot.target</filename>.</para>
159 <term><filename>cryptsetup.target</filename></term>
161 <para>A target that pulls in
162 setup services for all
168 <term><filename>dbus.service</filename></term>
170 <para>A special unit for the
171 D-Bus bus daemon. As soon as
172 this service is fully started
173 up systemd will connect to it
179 <term><filename>dbus.socket</filename></term>
181 <para>A special unit for the
182 D-Bus system bus socket. All
184 <varname>Type=dbus</varname>
191 <term><filename>default.target</filename></term>
193 <para>The default unit systemd
194 starts at bootup. Usually this
195 should be aliased (symlinked)
197 <filename>multi-user.target</filename>
199 <filename>graphical.target</filename>.</para>
201 <para>The default unit systemd
202 starts at bootup can be
204 <varname>systemd.unit=</varname>
205 kernel command line option.</para>
209 <term><filename>display-manager.service</filename></term>
211 <para>The display manager
212 service. Usually this should
213 be aliased (symlinked) to
214 <filename>gdm.service</filename>
215 or a similar display manager
220 <term><filename>emergency.target</filename></term>
222 <para>A special target unit
223 that starts an emergency
225 console. This unit is supposed
226 to be used with the kernel
228 <varname>systemd.unit=</varname>
229 and has otherwise little use.
234 <term><filename>final.target</filename></term>
236 <para>A special target unit
237 that is used during the
238 shutdown logic and may be used
239 to pull in late services after
240 all normal services are
241 already terminated and all
247 <term><filename>getty.target</filename></term>
249 <para>A special target unit
250 that pulls in statically
252 <filename>getty</filename>
258 <term><filename>graphical.target</filename></term>
260 <para>A special target unit
261 for setting up a graphical
262 login screen. This pulls in
263 <filename>multi-user.target</filename>.</para>
265 <para>Units that are needed
266 for graphical logins shall add
267 <varname>Wants=</varname>
268 dependencies for their unit to
270 <filename>multi-user.target</filename>)
271 during installation. This is
273 <varname>WantedBy=graphical.target</varname>
275 <literal>[Install]</literal>
280 <term><filename>hibernate.target</filename></term>
282 <para>A special target unit
284 system. This pulls in
285 <filename>sleep.target</filename>.</para>
289 <term><filename>hybrid-sleep.target</filename></term>
291 <para>A special target unit
292 for hibernating and suspending the
293 system at the same time. This pulls in
294 <filename>sleep.target</filename>.</para>
298 <term><filename>halt.target</filename></term>
300 <para>A special target unit
301 for shutting down and halting
302 the system. Note that this
303 target is distinct from
304 <filename>poweroff.target</filename>
305 in that it generally really
306 just halts the system rather
307 than powering it down.</para>
309 <para>Applications wanting to
310 halt the system should start
315 <term><filename>initrd-fs.target</filename></term>
317 <para><citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>3</manvolnum></citerefentry>
320 <varname>Before=</varname> to
321 <filename>sysroot-usr.mount</filename>
322 and all mount points found in
323 <filename>/etc/fstab</filename>
325 <option>auto</option> and
326 <option>x-initrd.mount</option>
332 <term><filename>kbrequest.target</filename></term>
334 <para>systemd starts this
335 target whenever Alt+ArrowUp is
336 pressed on the console. This
337 is a good candidate to be
338 aliased (symlinked) to
339 <filename>rescue.target</filename>.</para>
343 <term><filename>kexec.target</filename></term>
345 <para>A special target unit
346 for shutting down and rebooting the system via kexec.</para>
348 <para>Applications wanting to
349 reboot the system with kexec should start
354 <term><filename>local-fs.target</filename></term>
356 <para><citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>3</manvolnum></citerefentry>
359 <varname>Before=</varname> to
360 all mount units that refer to
361 local mount points for this
362 target unit. In addition, it
363 adds dependencies of type
364 <varname>Wants=</varname> to
365 this target unit for those
367 <filename>/etc/fstab</filename>
369 <option>auto</option> mount
374 <term><filename>multi-user.target</filename></term>
376 <para>A special target unit
377 for setting up a multi-user
378 system (non-graphical). This
380 <filename>graphical.target</filename>.</para>
382 <para>Units that are needed
383 for a multi-user system shall
384 add <varname>Wants=</varname>
385 dependencies for their unit to
387 installation. This is best
389 <varname>WantedBy=multi-user.target</varname>
391 <literal>[Install]</literal>
396 <term><filename>network-online.target</filename></term>
398 <para>Units that strictly
399 require a configured network
400 connection should pull in
401 <filename>network-online.target</filename>
403 <varname>Wants=</varname> type
404 dependency) and order
405 themselves after it. This
406 target unit is intended to
407 pull in a service that delays
408 further execution until the
409 network is sufficiently set
410 up. What precisely this
411 requires is left to the
412 implementation of the network
413 managing service.</para>
415 <para>Note the distinction
416 between this unit and
417 <filename>network.target</filename>. This
418 unit is an active unit
419 (i.e. pulled in by the
420 consumer rather than the
422 functionality) and pulls in a
423 service which possibly adds
424 substantial delays to further
425 execution. In contrast,
426 <filename>network.target</filename>
427 is a passive unit (i.e. pulled
428 in by the provider of the
429 functionality, rather than the
430 consumer) that usually does
433 <filename>network.target</filename>
434 is part of the boot of most
436 <filename>network-online.target</filename>
437 is not, except when at least
438 one unit requires it. Also see
440 url="http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget">Running
441 Services After the Network is
445 <para>All mount units for
446 remote network file systems
447 automatically pull in this
448 unit, and order themselves
449 after it. Note that networking
450 daemons that simply provide
451 functionality to other hosts
452 generally do not need to pull
457 <term><filename>paths.target</filename></term>
459 <para>A special target unit
460 that sets up all path units
462 <citerefentry><refentrytitle>systemd.path</refentrytitle><manvolnum>5</manvolnum></citerefentry>
463 for details) that shall be
464 active after boot.</para>
466 <para>It is recommended that
467 path units installed by
468 applications get pulled in via
469 <varname>Wants=</varname>
470 dependencies from this
471 unit. This is best configured
473 <varname>WantedBy=paths.target</varname>
475 <literal>[Install]</literal>
480 <term><filename>poweroff.target</filename></term>
482 <para>A special target unit
483 for shutting down and powering off the system.</para>
485 <para>Applications wanting to
486 power off the system should start
489 <para><filename>runlevel0.target</filename>
490 is an alias for this target
491 unit, for compatibility with SysV.</para>
495 <term><filename>reboot.target</filename></term>
497 <para>A special target unit
498 for shutting down and rebooting the system.</para>
500 <para>Applications wanting to
501 reboot the system should start
504 <para><filename>runlevel6.target</filename>
505 is an alias for this target
506 unit, for compatibility with SysV.</para>
510 <term><filename>remote-fs.target</filename></term>
513 <filename>local-fs.target</filename>,
517 <para>systemd automatically
518 adds dependencies of type
519 <varname>After=</varname> for
520 this target unit to all SysV
521 init script service units with
522 an LSB header referring to the
523 <literal>$remote_fs</literal>
528 <term><filename>rescue.target</filename></term>
530 <para>A special target unit
531 for setting up the base system
532 and a rescue shell.</para>
534 <para><filename>runlevel1.target</filename>
535 is an alias for this target
536 unit, for compatibility with SysV.</para>
540 <term><filename>initrd-root-fs.target</filename></term>
542 <para><citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>3</manvolnum></citerefentry>
545 <varname>Before=</varname> to
547 <filename>sysroot.mount</filename>
548 unit, which is generated from
549 the kernel command line.
554 <term><filename>runlevel2.target</filename></term>
555 <term><filename>runlevel3.target</filename></term>
556 <term><filename>runlevel4.target</filename></term>
557 <term><filename>runlevel5.target</filename></term>
559 <para>These are targets that
560 are called whenever the SysV
561 compatibility code asks for
563 respectively. It is a good
564 idea to make this an alias for
566 <filename>multi-user.target</filename>
568 <filename>graphical.target</filename>
573 <term><filename>shutdown.target</filename></term>
575 <para>A special target unit
576 that terminates the services
577 on system shutdown.</para>
579 <para>Services that shall be
580 terminated on system shutdown
581 shall add <varname>Conflicts=</varname>
582 dependencies to this unit for
583 their service unit, which is
585 <varname>DefaultDependencies=yes</varname>
586 is set (the default).</para>
590 <term><filename>sigpwr.target</filename></term>
592 <para>A special target that is
593 started when systemd receives
594 the SIGPWR process signal,
595 which is normally sent by the
596 kernel or UPS daemons when
601 <term><filename>sleep.target</filename></term>
603 <para>A special target unit
605 <filename>suspend.target</filename>,
606 <filename>hibernate.target</filename>
608 <filename>hybrid-sleep.target</filename>
609 and may be used to hook units
615 <term><filename>sockets.target</filename></term>
617 <para>A special target unit
618 that sets up all socket
620 <citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry>
621 for details) that shall be
622 active after boot.</para>
624 <para>Services that can be
625 socket-activated shall add
626 <varname>Wants=</varname>
627 dependencies to this unit for
628 their socket unit during
629 installation. This is best
631 <varname>WantedBy=sockets.target</varname>
633 <literal>[Install]</literal>
638 <term><filename>suspend.target</filename></term>
640 <para>A special target unit
642 system. This pulls in
643 <filename>sleep.target</filename>.</para>
647 <term><filename>swap.target</filename></term>
650 <filename>local-fs.target</filename>, but for swap
656 <term><filename>sysinit.target</filename></term>
658 <para>A special target unit
659 covering early boot-up scripts.</para>
663 <term><filename>syslog.socket</filename></term>
665 <para>The socket unit
666 syslog implementations should
667 listen on. All userspace log
668 messages will be made
669 available on this socket. For
670 more information about syslog
671 integration, please consult
673 url="http://www.freedesktop.org/wiki/Software/systemd/syslog">Syslog
679 <term><filename>system-update.target</filename></term>
681 <para>A special target unit
682 that is used for off-line
684 <citerefentry><refentrytitle>systemd-system-update-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>
685 will redirect the boot process
687 <filename>/system-update</filename>
688 exists. For more information
690 url="http://freedesktop.org/wiki/Software/systemd/SystemUpdates">System
692 Specification</ulink>.</para>
696 <term><filename>timers.target</filename></term>
698 <para>A special target unit
699 that sets up all timer
701 <citerefentry><refentrytitle>systemd.timer</refentrytitle><manvolnum>5</manvolnum></citerefentry>
702 for details) that shall be
703 active after boot.</para>
705 <para>It is recommended that
706 timer units installed by
707 applications get pulled in via
708 <varname>Wants=</varname>
709 dependencies from this
710 unit. This is best configured
712 <varname>WantedBy=timers.target</varname>
714 <literal>[Install]</literal>
719 <term><filename>umount.target</filename></term>
721 <para>A special target unit
722 that umounts all mount and
723 automount points on system
726 <para>Mounts that shall be
727 unmounted on system shutdown
729 dependencies to this unit for
730 their mount unit, which is
732 <varname>DefaultDependencies=yes</varname>
733 is set (the default).</para>
741 <title>Special System Units for Devices</title>
743 <para>Some target units are automatically pulled in as
744 devices of certain kinds show up in the system. These
745 may be used to automatically activate various services
746 based on the specific type of the available
751 <term><filename>bluetooth.target</filename></term>
753 <para>This target is started
754 automatically as soon as a
755 Bluetooth controller is
756 plugged in or becomes
757 available at boot.</para>
759 <para>This may be used to pull
760 in Bluetooth management
761 daemons dynamically when
762 Bluetooth hardware is
767 <term><filename>printer.target</filename></term>
769 <para>This target is started
770 automatically as soon as a
771 printer is plugged in or
775 <para>This may be used to pull
776 in printer management
777 daemons dynamically when
783 <term><filename>smartcard.target</filename></term>
785 <para>This target is started
786 automatically as soon as a
787 smartcard controller is
788 plugged in or becomes
789 available at boot.</para>
791 <para>This may be used to pull
792 in smartcard management
793 daemons dynamically when
794 smartcard hardware is
799 <term><filename>sound.target</filename></term>
801 <para>This target is started
802 automatically as soon as a
803 sound card is plugged in or
807 <para>This may be used to pull
808 in audio management daemons
809 dynamically when audio
810 hardware is found.</para>
817 <title>Special Passive System Units </title>
819 <para>A number of special system targets are defined
820 that can be used to properly order boot-up of optional
821 services. These targets are generally not part of the
822 initial boot transaction, unless they are explicitly
823 pulled in by one of the implementing services. Note
824 specifically that these <emphasis>passive</emphasis>
825 target units are generally not pulled in by the
826 consumer of a service, but by the provider of the
827 service. This means: a consuming service should order
828 itself after these targets (as appropriate), but not
829 pull it in. A providing service should order itself
830 before these targets (as appropriate) and pull it in
831 (via a <varname>Wants=</varname> type
834 <para>Note that these passive units cannot be started
835 manually, i.e. <literal>systemctl start
836 time-sync.target</literal> will fail with an
837 error. They can only be pulled in by dependency. This
838 is enforced since they exist for ordering purposes
839 only and thus are not useful as only unit within a
844 <term><filename>local-fs-pre.target</filename></term>
846 <para>This target unit is
847 automatically ordered before
848 all local mount points marked
849 with <option>auto</option>
850 (see above). It can be used to
851 execute certain units before
852 all local mounts.</para>
856 <term><filename>network.target</filename></term>
858 <para>This unit is supposed to
859 indicate when network
860 functionality is available,
861 but it is only very weakly
862 defined what that is supposed
863 to mean, with one exception:
864 at shutdown, a unit that is
866 <filename>network.target</filename>
867 will be stopped before the
868 network -- to whatever level
869 it might be set up then -- is
870 shut down. It is hence useful
871 when writing service files
872 that require network access on
873 shutdown, which should order
874 themselves after this target,
875 but not pull it in. Also see
877 url="http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget">Running
878 Services After the Network is
880 information. Also see
881 <filename>network-online.target</filename>
882 described above.</para>
884 <para>systemd automatically
885 adds dependencies of type
886 <varname>After=</varname> for
887 this target unit to all SysV
888 init script service units with
889 an LSB header referring to the
890 <literal>$network</literal>
895 <term><filename>network-pre.target</filename></term>
897 <para>This passive target unit
898 may be pulled in by services
899 that want to run before any
900 network is set up, for example
901 for the purpose of setting up a
902 firewall. All network
903 management software orders
904 itself after this target, but
905 does not pull it in.</para>
909 <term><filename>nss-lookup.target</filename></term>
911 <para>A target that should be
912 used as synchronization point
913 for all host/network name
914 service lookups. Note that
915 this is independent of
916 user/group name lookups for
918 <filename>nss-user-lookup.target</filename>
919 should be used. All services
920 for which the availability of
921 full host/network name
922 resolution is essential should
923 be ordered after this target,
924 but not pull it in. systemd
927 <varname>After=</varname> for
928 this target unit to all SysV
929 init script service units with
930 an LSB header referring to the
931 <literal>$named</literal>
936 <term><filename>nss-user-lookup.target</filename></term>
938 <para>A target that should be
939 used as synchronization point
940 for all user/group name
941 service lookups. Note that
942 this is independent of
943 host/network name lookups for
945 <filename>nss-lookup.target</filename>
946 should be used. All services
947 for which the availability of
948 the full user/group database is
949 essential should be ordered
950 after this target, but not
951 pull it in. Note that system
952 users are always resolvable,
953 and hence do not require any
954 special ordering against this
959 <term><filename>remote-fs-pre.target</filename></term>
961 <para>This target unit is
962 automatically ordered before
963 all remote mount point units
964 (see above). It can be used to
965 run certain units before the
967 established. Note that this
968 unit is generally not part of
969 the initial transaction,
970 unless the unit that wants to
971 be ordered before all remote
972 mounts pulls it in via a
973 <varname>Wants=</varname> type
974 dependency. If the unit wants
975 to be pulled in by the first
976 remote mount showing up, it
978 <filename>network-online.target</filename>
983 <term><filename>rpcbind.target</filename></term>
985 <para>The portmapper/rpcbind
986 pulls in this target and
987 orders itself before it, to
989 availability. systemd
992 <varname>After=</varname> for
993 this target unit to all SysV
994 init script service units with
995 an LSB header referring to the
996 <literal>$portmap</literal>
1001 <term><filename>time-sync.target</filename></term>
1003 <para>Services responsible for
1004 synchronizing the system clock
1005 from a remote source (such as
1006 NTP client implementations)
1007 should pull in this target and
1008 order themselves before
1009 it. All services where correct
1010 time is essential should be
1011 ordered after this unit, but
1012 not pull it in. systemd
1014 dependencies of type
1015 <varname>After=</varname> for
1016 this target unit to all SysV
1017 init script service units with
1018 an LSB header referring to the
1019 <literal>$time</literal>
1027 <title>Special User Units</title>
1029 <para>When systemd runs as a user instance, the
1030 following special units are available, which have
1031 similar definitions as their system counterparts:
1032 <filename>default.target</filename>,
1033 <filename>shutdown.target</filename>,
1034 <filename>sockets.target</filename>,
1035 <filename>timers.target</filename>,
1036 <filename>paths.target</filename>,
1037 <filename>bluetooth.target</filename>,
1038 <filename>printer.target</filename>,
1039 <filename>smartcard.target</filename>,
1040 <filename>sound.target</filename>.</para>
1042 <para>In addition, the following special unit is
1043 understood only when systemd runs as service instance:</para>
1047 <term><filename>exit.target</filename></term>
1049 <para>A special service unit
1050 for shutting down the
1051 user service manager.</para>
1053 <para>Applications wanting to
1054 terminate the user service
1055 manager should start this
1056 unit. If systemd receives
1057 <constant>SIGTERM</constant> or <constant>SIGINT</constant> when running
1058 as user service daemon, it will
1059 start this unit.</para>
1061 <para>Normally, this pulls in
1062 <filename>shutdown.target</filename>
1063 which in turn should be
1064 conflicted by all units that
1065 want to be shut down on
1066 user service manager exit.</para>
1073 <title>Special Slice Units</title>
1075 <para>There are four <literal>.slice</literal> units
1076 which form the basis of the hierarchy for assignment
1077 of resources for services, users, and virtual machines
1078 or containers.</para>
1082 <term><filename>-.slice</filename></term>
1084 <para>The root slice is the
1085 root of the hierarchy. It
1086 usually does not contain units
1087 directly, but may be used to
1088 set defaults for the whole
1094 <term><filename>system.slice</filename></term>
1096 <para>By default, all services
1098 <command>systemd</command> are
1099 found in this slice.</para>
1104 <term><filename>user.slice</filename></term>
1106 <para>By default, all user
1107 processes and services started
1108 on behalf of the user,
1109 including the per-user systemd
1110 instance are found in this
1116 <term><filename>machine.slice</filename></term>
1118 <para>By defalt, all virtual
1119 machines and containers
1121 <command>systemd-machined</command>
1122 are found in this slice.
1130 <title>See Also</title>
1132 <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
1133 <citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
1134 <citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
1135 <citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
1136 <citerefentry><refentrytitle>systemd.target</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
1137 <citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
1138 <citerefentry><refentrytitle>bootup</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
1139 <citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>