1a38107941725211e7c3f051f7a8f5e12199f03acmaeder<?xml version='1.0'?> <!--*-nxml-*-->

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"

e9458b1a7a19a63aa4c179f9ab20f4d50681c168Jens Elkner "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu

fc05327b875b5723b6c17849b83477f29ec12c90Felix Gabriel Mance

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu<refentry id="systemd.special">

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <refentryinfo>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <title>systemd.special</title>

0dd6e7830de0887c9a12356447975a826b3b3db2Christian Maeder <productname>systemd</productname>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu

e0f1794e365dd347e97b37d7d22b2fce27296fa1Christian Maeder <authorgroup>

424860079d47bf490fa98d5d7498096a0447c569mcodescu <author>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <contrib>Developer</contrib>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <firstname>Lennart</firstname>

1a38107941725211e7c3f051f7a8f5e12199f03acmaeder <surname>Poettering</surname>

1a38107941725211e7c3f051f7a8f5e12199f03acmaeder <email>lennart@poettering.net</email>

32bbac77828be0233953f8fe476edb0a9585408dChristian Maeder </author>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </authorgroup>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </refentryinfo>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <refmeta>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <refentrytitle>systemd.special</refentrytitle>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <manvolnum>7</manvolnum>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </refmeta>

27fdf879983dd28e211b41f3be6c0e930b7c816bFelix Gabriel Mance

431571057e88a650a974adec93ea4bb5173b6213Felix Gabriel Mance <refnamediv>

1a38107941725211e7c3f051f7a8f5e12199f03acmaeder <refname>systemd.special</refname>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <refpurpose>Special systemd units</refpurpose>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </refnamediv>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <refsynopsisdiv>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <para><filename>basic.target</filename>,

b84c87f199dc287d235d7dad6ea344f6912ef531Christian Maeder <filename>bluetooth.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>ctrl-alt-del.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>cryptsetup.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>cryptsetup-pre.target</filename>,

be00381168b3f10192afabbba136fb06d3a9f358Christian Maeder <filename>dbus.service</filename>,

be00381168b3f10192afabbba136fb06d3a9f358Christian Maeder <filename>dbus.socket</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>default.target</filename>,

27fdf879983dd28e211b41f3be6c0e930b7c816bFelix Gabriel Mance <filename>display-manager.service</filename>,

7852de3551fc797566ee71165bafe05b6d81728cnotanartist <filename>emergency.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>exit.target</filename>,

27fdf879983dd28e211b41f3be6c0e930b7c816bFelix Gabriel Mance <filename>final.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>getty.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>graphical.target</filename>,

27fdf879983dd28e211b41f3be6c0e930b7c816bFelix Gabriel Mance <filename>halt.target</filename>,

d0f58d27c2536eba454d8f77de8617bc6a2c99cdFelix Gabriel Mance <filename>hibernate.target</filename>,

d0f58d27c2536eba454d8f77de8617bc6a2c99cdFelix Gabriel Mance <filename>hybrid-sleep.target</filename>,

d0f58d27c2536eba454d8f77de8617bc6a2c99cdFelix Gabriel Mance <filename>initrd-fs.target</filename>,

d0f58d27c2536eba454d8f77de8617bc6a2c99cdFelix Gabriel Mance <filename>kbrequest.target</filename>,

431571057e88a650a974adec93ea4bb5173b6213Felix Gabriel Mance <filename>kexec.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>local-fs.target</filename>,

27fdf879983dd28e211b41f3be6c0e930b7c816bFelix Gabriel Mance <filename>local-fs-pre.target</filename>,

424860079d47bf490fa98d5d7498096a0447c569mcodescu <filename>multi-user.target</filename>,

60f30f0eeeacdfc1e0dfe39664373ddf5a0675adFelix Gabriel Mance <filename>network.target</filename>,

60f30f0eeeacdfc1e0dfe39664373ddf5a0675adFelix Gabriel Mance <filename>network-online.target</filename>,

0dd6e7830de0887c9a12356447975a826b3b3db2Christian Maeder <filename>network-pre.target</filename>,

424860079d47bf490fa98d5d7498096a0447c569mcodescu <filename>nss-lookup.target</filename>,

424860079d47bf490fa98d5d7498096a0447c569mcodescu <filename>nss-user-lookup.target</filename>,

424860079d47bf490fa98d5d7498096a0447c569mcodescu <filename>paths.target</filename>,

60f30f0eeeacdfc1e0dfe39664373ddf5a0675adFelix Gabriel Mance <filename>poweroff.target</filename>,

d6d81ead61a5f9fb7d047e623f7898e730c258camcodescu <filename>printer.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>reboot.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>remote-fs.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>remote-fs-pre.target</filename>,

60f30f0eeeacdfc1e0dfe39664373ddf5a0675adFelix Gabriel Mance <filename>rescue.target</filename>,

7852de3551fc797566ee71165bafe05b6d81728cnotanartist <filename>initrd-root-fs.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>rpcbind.target</filename>,

60f30f0eeeacdfc1e0dfe39664373ddf5a0675adFelix Gabriel Mance <filename>runlevel2.target</filename>,

9475501a6acf48434052d9e6f4a05ed6681eaaabFrancisc Nicolae Bungiu <filename>runlevel3.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>runlevel4.target</filename>,

7852de3551fc797566ee71165bafe05b6d81728cnotanartist <filename>runlevel5.target</filename>,

80875f917d741946a39d0ec0b5721e46ba609823Till Mossakowski <filename>shutdown.target</filename>,

80875f917d741946a39d0ec0b5721e46ba609823Till Mossakowski <filename>sigpwr.target</filename>,

424860079d47bf490fa98d5d7498096a0447c569mcodescu <filename>sleep.target</filename>,

0dd6e7830de0887c9a12356447975a826b3b3db2Christian Maeder <filename>slices.target</filename>,

0dd6e7830de0887c9a12356447975a826b3b3db2Christian Maeder <filename>smartcard.target</filename>,

424860079d47bf490fa98d5d7498096a0447c569mcodescu <filename>sockets.target</filename>,

0dd6e7830de0887c9a12356447975a826b3b3db2Christian Maeder <filename>sound.target</filename>,

0dd6e7830de0887c9a12356447975a826b3b3db2Christian Maeder <filename>suspend.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>swap.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>sysinit.target</filename>,

d0f58d27c2536eba454d8f77de8617bc6a2c99cdFelix Gabriel Mance <filename>syslog.socket</filename>,

60f30f0eeeacdfc1e0dfe39664373ddf5a0675adFelix Gabriel Mance <filename>system-update.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>time-sync.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>timers.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>umount.target</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>-.slice</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>system.slice</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>user.slice</filename>,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>machine.slice</filename></para>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </refsynopsisdiv>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <refsect1>

3d3889e0cefcdce9b3f43c53aaa201943ac2e895Jonathan von Schroeder <title>Description</title>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu

3d3889e0cefcdce9b3f43c53aaa201943ac2e895Jonathan von Schroeder <para>A few units are treated specially by systemd. They have

3d3889e0cefcdce9b3f43c53aaa201943ac2e895Jonathan von Schroeder special internal semantics and cannot be renamed.</para>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </refsect1>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <refsect1>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <title>Special System Units</title>

3d3889e0cefcdce9b3f43c53aaa201943ac2e895Jonathan von Schroeder

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <variablelist>

31e9d2a02e15b7dbc157e0d3fb3b84f6c8666482Christian Maeder <varlistentry>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <term><filename>basic.target</filename></term>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <listitem>

656f17ae9b7610ff2de1b6eedeeadea0c3bcdc8dChristian Maeder <para>A special target unit covering basic boot-up.</para>

d3cb3401882f6956de016f8eecbec1cd3b868acbFelix Gabriel Mance

d3cb3401882f6956de016f8eecbec1cd3b868acbFelix Gabriel Mance <para>systemd automatically adds dependencies of the types

d3cb3401882f6956de016f8eecbec1cd3b868acbFelix Gabriel Mance <varname>Requires=</varname> and <varname>After=</varname>

d3cb3401882f6956de016f8eecbec1cd3b868acbFelix Gabriel Mance for this target unit to all services (except for those with

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <varname>DefaultDependencies=no</varname>).</para>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <para>Usually, this should pull-in all local mount points plus

7852de3551fc797566ee71165bafe05b6d81728cnotanartist <filename>/var</filename>, <filename>/tmp</filename> and

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>/var/tmp</filename>, swap devices, sockets, timers,

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu path units and other basic initialization necessary for general

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu purpose daemons. The mentioned mount points are special cased

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu to allow them to be remote.

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </para>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu

0dd6e7830de0887c9a12356447975a826b3b3db2Christian Maeder <para>This target usually does not pull in any non-target units

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu directly, but rather does so indirectly via other early boot targets.

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu It is instead meant as a synchronization point for late boot

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu services. Refer to

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <citerefentry><refentrytitle>bootup</refentrytitle><manvolnum>7</manvolnum></citerefentry>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu for details on the targets involved.

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </para>

06acd8a23b2f06e7b2373d53f738cf56c7f03223Francisc Nicolae Bungiu

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </listitem>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </varlistentry>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <varlistentry>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <term><filename>ctrl-alt-del.target</filename></term>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <listitem>

7852de3551fc797566ee71165bafe05b6d81728cnotanartist <para>systemd starts this target whenever Control+Alt+Del is

32bbac77828be0233953f8fe476edb0a9585408dChristian Maeder pressed on the console. Usually, this should be aliased

80875f917d741946a39d0ec0b5721e46ba609823Till Mossakowski (symlinked) to <filename>reboot.target</filename>.</para>

80875f917d741946a39d0ec0b5721e46ba609823Till Mossakowski </listitem>

80875f917d741946a39d0ec0b5721e46ba609823Till Mossakowski </varlistentry>

80875f917d741946a39d0ec0b5721e46ba609823Till Mossakowski <varlistentry>

32bbac77828be0233953f8fe476edb0a9585408dChristian Maeder <term><filename>cryptsetup.target</filename></term>

80875f917d741946a39d0ec0b5721e46ba609823Till Mossakowski <listitem>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <para>A target that pulls in setup services for all

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder encrypted block devices.</para>

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder </listitem>

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder </varlistentry>

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder <varlistentry>

b84c87f199dc287d235d7dad6ea344f6912ef531Christian Maeder <term><filename>dbus.service</filename></term>

7852de3551fc797566ee71165bafe05b6d81728cnotanartist <listitem>

80875f917d741946a39d0ec0b5721e46ba609823Till Mossakowski <para>A special unit for the D-Bus bus daemon. As soon as

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder this service is fully started up systemd will connect to it

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder and register its service.</para>

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder </listitem>

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder </varlistentry>

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder <varlistentry>

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder <term><filename>dbus.socket</filename></term>

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder <listitem>

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder <para>A special unit for the D-Bus system bus socket. All

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder units with <varname>Type=dbus</varname> automatically gain a

cf0439f74f1d55a9840d38a88f9b0f4fc00d5547Christian Maeder dependency on this unit.</para>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </listitem>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </varlistentry>

7852de3551fc797566ee71165bafe05b6d81728cnotanartist <varlistentry>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <term><filename>default.target</filename></term>

7852de3551fc797566ee71165bafe05b6d81728cnotanartist <listitem>

80875f917d741946a39d0ec0b5721e46ba609823Till Mossakowski <para>The default unit systemd starts at bootup. Usually,

624f8c31bd8d6746b93f4b5966aa6fc7680fefc5Felix Gabriel Mance this should be aliased (symlinked) to

80875f917d741946a39d0ec0b5721e46ba609823Till Mossakowski <filename>multi-user.target</filename> or

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <filename>graphical.target</filename>.</para>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu <para>The default unit systemd starts at bootup can be

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu overridden with the <varname>systemd.unit=</varname> kernel

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu command line option.</para>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </listitem>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </varlistentry>

b84c87f199dc287d235d7dad6ea344f6912ef531Christian Maeder <varlistentry>

624f8c31bd8d6746b93f4b5966aa6fc7680fefc5Felix Gabriel Mance <term><filename>display-manager.service</filename></term>

7852de3551fc797566ee71165bafe05b6d81728cnotanartist <listitem>

624f8c31bd8d6746b93f4b5966aa6fc7680fefc5Felix Gabriel Mance <para>The display manager service. Usually, this should be

1a38107941725211e7c3f051f7a8f5e12199f03acmaeder aliased (symlinked) to <filename>gdm.service</filename> or a

80875f917d741946a39d0ec0b5721e46ba609823Till Mossakowski similar display manager service.</para>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </listitem>

ee93ea764a2b8189253e912c8447f9419033f6d4Francisc Nicolae Bungiu </varlistentry>

d0f58d27c2536eba454d8f77de8617bc6a2c99cdFelix Gabriel Mance <varlistentry>

431571057e88a650a974adec93ea4bb5173b6213Felix Gabriel Mance <term><filename>emergency.target</filename></term>

431571057e88a650a974adec93ea4bb5173b6213Felix Gabriel Mance <listitem>

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu <para>A special target unit that starts an emergency shell

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu on the main console. This unit is supposed to be used with

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu the kernel command line option

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu <varname>systemd.unit=</varname> and has otherwise little

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu use.

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu </para>

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu </listitem>

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu </varlistentry>

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu <varlistentry>

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu <term><filename>exit.target</filename></term>

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu <listitem>

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu <para>A special service unit for shutting down the system or

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu user service manager. It is equivalent to

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu <filename>poweroff.target</filename> on non-container

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu systems, and also works in containers.</para>

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu <para>systemd will start this unit when it receives a

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu request to shut down over D-Bus or a

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu <constant>SIGTERM</constant> or <constant>SIGINT</constant>

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu signal when running as user service daemon.</para>

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu <para>Normally, this (indirectly) pulls in

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu <filename>shutdown.target</filename>, which in turn should be

b90f0b7fd6ccfbdd7e5adb65b1f6c02c7758ff5cmcodescu conflicted by all units that want to be scheduled for

shutdown when the service manager starts to exit.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>final.target</filename></term>

<listitem>

<para>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.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>getty.target</filename></term>

<listitem>

<para>A special target unit that pulls in statically

configured local TTY <filename>getty</filename> instances.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>graphical.target</filename></term>

<listitem>

<para>A special target unit for setting up a graphical login

screen. This pulls in

<filename>multi-user.target</filename>.</para>

<para>Units that are needed for graphical logins shall add

<varname>Wants=</varname> dependencies for their unit to

this unit (or <filename>multi-user.target</filename>) during

installation. This is best configured via

<varname>WantedBy=graphical.target</varname> in the unit's

<literal>[Install]</literal> section.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>hibernate.target</filename></term>

<listitem>

<para>A special target unit for hibernating the system. This

pulls in <filename>sleep.target</filename>.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>hybrid-sleep.target</filename></term>

<listitem>

<para>A special target unit for hibernating and suspending

the system at the same time. This pulls in

<filename>sleep.target</filename>.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>halt.target</filename></term>

<listitem>

<para>A special target unit for shutting down and halting

the system. Note that this target is distinct from

<filename>poweroff.target</filename> in that it generally

really just halts the system rather than powering it

down.</para>

<para>Applications wanting to halt the system should start

this unit.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>initrd-fs.target</filename></term>

<listitem>

<para><citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>3</manvolnum></citerefentry>

automatically adds dependencies of type

<varname>Before=</varname> to

<filename>sysroot-usr.mount</filename> and all mount points

found in <filename>/etc/fstab</filename> that have

<option>x-initrd.mount</option> and not have

<option>noauto</option> mount options set.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>kbrequest.target</filename></term>

<listitem>

<para>systemd starts this target whenever Alt+ArrowUp is

pressed on the console. This is a good candidate to be

aliased (symlinked) to

<filename>rescue.target</filename>.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>kexec.target</filename></term>

<listitem>

<para>A special target unit for shutting down and rebooting

the system via kexec.</para>

<para>Applications wanting to reboot the system with kexec

should start this unit.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>local-fs.target</filename></term>

<listitem>

<para><citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>3</manvolnum></citerefentry>

automatically adds dependencies of type

<varname>Before=</varname> to all mount units that refer to

local mount points for this target unit. In addition, it

adds dependencies of type <varname>Wants=</varname> to this

target unit for those mounts listed in

<filename>/etc/fstab</filename> that have the

<option>auto</option> mount option set.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>multi-user.target</filename></term>

<listitem>

<para>A special target unit for setting up a multi-user

system (non-graphical). This is pulled in by

<filename>graphical.target</filename>.</para>

<para>Units that are needed for a multi-user system shall

add <varname>Wants=</varname> dependencies for their unit to

this unit during installation. This is best configured via

<varname>WantedBy=multi-user.target</varname> in the unit's

<literal>[Install]</literal> section.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>network-online.target</filename></term>

<listitem>

<para>Units that strictly require a configured network

connection should pull in

<filename>network-online.target</filename> (via a

<varname>Wants=</varname> 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.</para>

<para>Note the distinction between this unit and

<filename>network.target</filename>. 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, <filename>network.target</filename> 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, <filename>network.target</filename>

is part of the boot of most systems, while

<filename>network-online.target</filename> is not, except

when at least one unit requires it. Also see <ulink

url="http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget">Running

Services After the Network is up</ulink> for more

information.</para>

<para>All mount units for remote network file systems

automatically pull in this unit, and order themselves after

it. Note that networking daemons that simply provide

functionality to other hosts generally do not need to pull

this in.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>paths.target</filename></term>

<listitem>

<para>A special target unit that sets up all path units (see

<citerefentry><refentrytitle>systemd.path</refentrytitle><manvolnum>5</manvolnum></citerefentry>

for details) that shall be active after boot.</para>

<para>It is recommended that path units installed by

applications get pulled in via <varname>Wants=</varname>

dependencies from this unit. This is best configured via a

<varname>WantedBy=paths.target</varname> in the path unit's

<literal>[Install]</literal> section.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>poweroff.target</filename></term>

<listitem>

<para>A special target unit for shutting down and powering

off the system.</para>

<para>Applications wanting to power off the system should

start this unit.</para>

<para><filename>runlevel0.target</filename> is an alias for

this target unit, for compatibility with SysV.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>reboot.target</filename></term>

<listitem>

<para>A special target unit for shutting down and rebooting

the system.</para>

<para>Applications wanting to reboot the system should start

this unit.</para>

<para><filename>runlevel6.target</filename> is an alias for

this target unit, for compatibility with SysV.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>remote-fs.target</filename></term>

<listitem>

<para>Similar to <filename>local-fs.target</filename>, but

for remote mount points.</para>

<para>systemd automatically adds dependencies of type

<varname>After=</varname> for this target unit to all SysV

init script service units with an LSB header referring to

the <literal>$remote_fs</literal> facility.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>rescue.target</filename></term>

<listitem>

<para>A special target unit for setting up the base system

and a rescue shell.</para>

<para><filename>runlevel1.target</filename> is an alias for

this target unit, for compatibility with SysV.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>initrd-root-fs.target</filename></term>

<listitem>

<para><citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>3</manvolnum></citerefentry>

automatically adds dependencies of type

<varname>Before=</varname> to the

<filename>sysroot.mount</filename> unit, which is generated

from the kernel command line.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>runlevel2.target</filename></term>

<term><filename>runlevel3.target</filename></term>

<term><filename>runlevel4.target</filename></term>

<term><filename>runlevel5.target</filename></term>

<listitem>

<para>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) <filename>multi-user.target</filename>

(for runlevel 2) or <filename>graphical.target</filename>

(the others).</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>shutdown.target</filename></term>

<listitem>

<para>A special target unit that terminates the services on

system shutdown.</para>

<para>Services that shall be terminated on system shutdown

shall add <varname>Conflicts=</varname> dependencies to this

unit for their service unit, which is implicitly done when

<varname>DefaultDependencies=yes</varname> is set (the

default).</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>sigpwr.target</filename></term>

<listitem>

<para>A special target that is started when systemd receives

the SIGPWR process signal, which is normally sent by the

kernel or UPS daemons when power fails.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>sleep.target</filename></term>

<listitem>

<para>A special target unit that is pulled in by

<filename>suspend.target</filename>,

<filename>hibernate.target</filename> and

<filename>hybrid-sleep.target</filename> and may be used to

hook units into the sleep state logic.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>slices.target</filename></term>

<listitem>

<para>A special target unit that sets up all slice units (see

<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry> for

details) that shall be active after boot. By default the generic <filename>user.slice</filename>,

<filename>system.slice</filename>, <filename>machines.slice</filename> slice units, as well as the the root

slice unit <filename>-.slice</filename> are pulled in and ordered before this unit (see below).</para>

<para>It's a good idea to add <varname>WantedBy=slices.target</varname> lines to the <literal>[Install]</literal>

section of all slices units that may be installed dynamically.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>sockets.target</filename></term>

<listitem>

<para>A special target unit that sets up all socket

units (see

<citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry>

for details) that shall be active after boot.</para>

<para>Services that can be socket-activated shall add

<varname>Wants=</varname> dependencies to this unit for

their socket unit during installation. This is best

configured via a <varname>WantedBy=sockets.target</varname>

in the socket unit's <literal>[Install]</literal>

section.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>suspend.target</filename></term>

<listitem>

<para>A special target unit for suspending the system. This

pulls in <filename>sleep.target</filename>.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>swap.target</filename></term>

<listitem>

<para>Similar to <filename>local-fs.target</filename>, but

for swap partitions and swap files.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>sysinit.target</filename></term>

<listitem>

<para>This target pulls in the services required for system

initialization. System services pulled in by this target should

declare <varname>DefaultDependencies=no</varname> 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

<citerefentry><refentrytitle>bootup</refentrytitle><manvolnum>7</manvolnum></citerefentry>.

</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>syslog.socket</filename></term>

<listitem>

<para>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 <ulink

url="http://www.freedesktop.org/wiki/Software/systemd/syslog">Syslog

Interface</ulink> document.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>system-update.target</filename></term>

<listitem>

<para>A special target unit that is used for off-line system

updates.

<citerefentry><refentrytitle>systemd-system-update-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>

will redirect the boot process to this target if

<filename>/system-update</filename> exists. For more

information see the <ulink

url="http://freedesktop.org/wiki/Software/systemd/SystemUpdates">System

Updates Specification</ulink>.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>timers.target</filename></term>

<listitem>

<para>A special target unit that sets up all timer units

(see

<citerefentry><refentrytitle>systemd.timer</refentrytitle><manvolnum>5</manvolnum></citerefentry>

for details) that shall be active after boot.</para>

<para>It is recommended that timer units installed by

applications get pulled in via <varname>Wants=</varname>

dependencies from this unit. This is best configured via

<varname>WantedBy=timers.target</varname> in the timer

unit's <literal>[Install]</literal> section.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>umount.target</filename></term>

<listitem>

<para>A special target unit that unmounts all mount and

automount points on system shutdown.</para>

<para>Mounts that shall be unmounted on system shutdown

shall add Conflicts dependencies to this unit for their

mount unit, which is implicitly done when

<varname>DefaultDependencies=yes</varname> is set (the

default).</para>

</listitem>

</varlistentry>

</variablelist>

</refsect1>

<refsect1>

<title>Special System Units for Devices</title>

<para>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.</para>

<variablelist>

<varlistentry>

<term><filename>bluetooth.target</filename></term>

<listitem>

<para>This target is started automatically as soon as a

Bluetooth controller is plugged in or becomes available at

boot.</para>

<para>This may be used to pull in Bluetooth management

daemons dynamically when Bluetooth hardware is found.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>printer.target</filename></term>

<listitem>

<para>This target is started automatically as soon as a

printer is plugged in or becomes available at boot.</para>

<para>This may be used to pull in printer management daemons

dynamically when printer hardware is found.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>smartcard.target</filename></term>

<listitem>

<para>This target is started automatically as soon as a

smartcard controller is plugged in or becomes available at

boot.</para>

<para>This may be used to pull in smartcard management

daemons dynamically when smartcard hardware is found.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>sound.target</filename></term>

<listitem>

<para>This target is started automatically as soon as a

sound card is plugged in or becomes available at

boot.</para>

<para>This may be used to pull in audio management daemons

dynamically when audio hardware is found.</para>

</listitem>

</varlistentry>

</variablelist>

</refsect1>

<refsect1>

<title>Special Passive System Units </title>

<para>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 <emphasis>passive</emphasis> 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

<varname>Wants=</varname> type dependency).</para>

<para>Note that these passive units cannot be started manually,

i.e. <literal>systemctl start time-sync.target</literal> 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.</para>

<variablelist>

<varlistentry>

<term><filename>cryptsetup-pre.target</filename></term>

<listitem>

<para>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.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>local-fs-pre.target</filename></term>

<listitem>

<para>This target unit is

automatically ordered before

all local mount points marked

with <option>auto</option>

(see above). It can be used to

execute certain units before

all local mounts.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>network.target</filename></term>

<listitem>

<para>This unit is supposed to indicate when network

functionality is available, but it is only very weakly

defined what that is supposed to mean, with one exception:

at shutdown, a unit that is ordered after

<filename>network.target</filename> will be stopped before

the network -- to whatever level it might be set up then --

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

<ulink url="http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget">Running

Services After the Network is up</ulink> for more

information. Also see

<filename>network-online.target</filename> described

above.</para>

<para>systemd automatically adds dependencies of type

<varname>After=</varname> for this target unit to all SysV

init script service units with an LSB header referring to

the <literal>$network</literal> facility.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>network-pre.target</filename></term>

<listitem>

<para>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.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>nss-lookup.target</filename></term>

<listitem>

<para>A target that should be used as synchronization point

for all host/network name service lookups. Note that this is

independent of user/group name lookups for which

<filename>nss-user-lookup.target</filename> 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 <varname>After=</varname> for this

target unit to all SysV init script service units with an

LSB header referring to the <literal>$named</literal>

facility.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>nss-user-lookup.target</filename></term>

<listitem>

<para>A target that should be used as synchronization point

for all user/group name service lookups. Note that this is

independent of host/network name lookups for which

<filename>nss-lookup.target</filename> 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. Note that system users are always

resolvable, and hence do not require any special ordering

against this target.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>remote-fs-pre.target</filename></term>

<listitem>

<para>This target unit is automatically ordered before all

remote mount point units (see above). It can be used to run

certain units before the remote 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

<varname>Wants=</varname> type dependency. If the unit wants

to be pulled in by the first remote mount showing up, it

should use <filename>network-online.target</filename> (see

above).</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>rpcbind.target</filename></term>

<listitem>

<para>The portmapper/rpcbind pulls in this target and orders

itself before it, to indicate its availability. systemd

automatically adds dependencies of type

<varname>After=</varname> for this target unit to all SysV

init script service units with an LSB header referring to

the <literal>$portmap</literal> facility.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>time-sync.target</filename></term>

<listitem>

<para>Services responsible for synchronizing the system

clock from a remote source (such as NTP client

implementations) should pull in this target and order

themselves before it. All services where correct time is

essential should be ordered after this unit, but not pull it

in. systemd automatically adds dependencies of type

<varname>After=</varname> for this target unit to all SysV

init script service units with an LSB header referring to

the <literal>$time</literal> facility. </para>

</listitem>

</varlistentry>

</variablelist>

</refsect1>

<refsect1>

<title>Special User Units</title>

<para>When systemd runs as a user instance, the following special

units are available, which have similar definitions as their

system counterparts:

<filename>exit.target</filename>,

<filename>default.target</filename>,

<filename>shutdown.target</filename>,

<filename>sockets.target</filename>,

<filename>timers.target</filename>,

<filename>paths.target</filename>,

<filename>bluetooth.target</filename>,

<filename>printer.target</filename>,

<filename>smartcard.target</filename>,

<filename>sound.target</filename>.</para>

</refsect1>

<refsect1>

<title>Special Slice Units</title>

<para>There are four <literal>.slice</literal> units which form

the basis of the hierarchy for assignment of resources for

services, users, and virtual machines or containers.</para>

<variablelist>

<varlistentry>

<term><filename>-.slice</filename></term>

<listitem>

<para>The root slice is the root of the hierarchy. It

usually does not contain units directly, but may be used to

set defaults for the whole tree.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>system.slice</filename></term>

<listitem>

<para>By default, all system services started by

<command>systemd</command> are found in this slice.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>user.slice</filename></term>

<listitem>

<para>By default, all user processes and services started on

behalf of the user, including the per-user systemd instance

are found in this slice.</para>

</listitem>

</varlistentry>

<varlistentry>

<term><filename>machine.slice</filename></term>

<listitem>

<para>By default, all virtual machines and containers

registered with <command>systemd-machined</command> are

found in this slice.

</para>

</listitem>

</varlistentry>

</variablelist>

</refsect1>

<refsect1>

<title>See Also</title>

<para>

<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,

<citerefentry><refentrytitle>systemd.unit</refentrytitle><manvolnum>5</manvolnum></citerefentry>,

<citerefentry><refentrytitle>systemd.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>,

<citerefentry><refentrytitle>systemd.socket</refentrytitle><manvolnum>5</manvolnum></citerefentry>,

<citerefentry><refentrytitle>systemd.target</refentrytitle><manvolnum>5</manvolnum></citerefentry>,

<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>,

<citerefentry project='man-pages'><refentrytitle>bootup</refentrytitle><manvolnum>7</manvolnum></citerefentry>,

<citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>

</para>

</refsect1>

</refentry>