systemd.special.xml revision 013d8a39a6178179080bcfee9122b29cf9d29259
ab4ab2edaac480f68b476dc19e015c54cd4f1978Lubos Kosco<?xml version='1.0'?> <!--*-nxml-*-->
ab4ab2edaac480f68b476dc19e015c54cd4f1978Lubos Kosco<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
b227f89b8c13b15a9372ce56713c024f7f73be35Lubos Kosco "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
ab4ab2edaac480f68b476dc19e015c54cd4f1978Lubos Kosco
9661674ed58ba62a40e43d1a4b38d5e77c3c6545Knut Anders Hatlen<!--
9661674ed58ba62a40e43d1a4b38d5e77c3c6545Knut Anders Hatlen This file is part of systemd.
9661674ed58ba62a40e43d1a4b38d5e77c3c6545Knut Anders Hatlen
551b849ce88d596dc52dda2f78229a932b339c78Lubos Kosco Copyright 2010 Lennart Poettering
551b849ce88d596dc52dda2f78229a932b339c78Lubos Kosco
9661674ed58ba62a40e43d1a4b38d5e77c3c6545Knut Anders Hatlen systemd is free software; you can redistribute it and/or modify it
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye under the terms of the GNU Lesser General Public License as published by
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye the Free Software Foundation; either version 2.1 of the License, or
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye (at your option) any later version.
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye
477c09a2656e6a2c1075425ad81e61d594164fa9Lubos Kosco systemd is distributed in the hope that it will be useful, but
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye WITHOUT ANY WARRANTY; without even the implied warranty of
bcae302a5f4b516d2f3c05f657df054e1a0efde7Knut Anders Hatlen MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye Lesser General Public License for more details.
98774b0b90e4da0f3f2c5e4856bcbbf366ed0fe0Knut Anders Hatlen
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye You should have received a copy of the GNU Lesser General Public License
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye along with systemd; If not, see <http://www.gnu.org/licenses/>.
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye-->
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye
afb218f076cae538126a5f931299a82a114a075aKnut Anders Hatlen<refentry id="systemd.special">
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <refentryinfo>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <title>systemd.special</title>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <productname>systemd</productname>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <authorgroup>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <author>
c0550b01024b910b8c1468811c0ea663b10b1372Trond Norbye <contrib>Developer</contrib>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <firstname>Lennart</firstname>
ab4ab2edaac480f68b476dc19e015c54cd4f1978Lubos Kosco <surname>Poettering</surname>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <email>lennart@poettering.net</email>
9661674ed58ba62a40e43d1a4b38d5e77c3c6545Knut Anders Hatlen </author>
bbb39d08c0e5b73c89ba813a7c1789842c60f961Lubos Kosco </authorgroup>
2ba599c0d79caf59996d8b54a0490bb968442134Knut Anders Hatlen </refentryinfo>
67b14513c549ae0027ba7590e736b3dd3281db7cLubos Kosco
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <refmeta>
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <refentrytitle>systemd.special</refentrytitle>
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <manvolnum>7</manvolnum>
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco </refmeta>
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <refnamediv>
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <refname>systemd.special</refname>
eb82bbbf6f8bff3b3d747c8aa06c8ab16f87ea94Lubos Kosco <refpurpose>Special systemd units</refpurpose>
6d7c6f82e644c205bc679ee5b1fa2929ec949963Lubos Kosco </refnamediv>
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <refsynopsisdiv>
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <para><filename>basic.target</filename>,
6d7c6f82e644c205bc679ee5b1fa2929ec949963Lubos Kosco <filename>bluetooth.target</filename>,
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <filename>ctrl-alt-del.target</filename>,
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <filename>cryptsetup.target</filename>,
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <filename>dbus.service</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>dbus.socket</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>default.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>display-manager.service</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>emergency.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>exit.service</filename>,
9661674ed58ba62a40e43d1a4b38d5e77c3c6545Knut Anders Hatlen <filename>final.service</filename>,
bbb39d08c0e5b73c89ba813a7c1789842c60f961Lubos Kosco <filename>getty.target</filename>,
2ba599c0d79caf59996d8b54a0490bb968442134Knut Anders Hatlen <filename>graphical.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>hibernate.target</filename>,
ca37bb3c4127b35d333203398bd983ee730d9da5Jan S Berg <filename>http-daemon.target</filename>,
6d7c6f82e644c205bc679ee5b1fa2929ec949963Lubos Kosco <filename>halt.target</filename>,
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <filename>kbrequest.target</filename>,
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <filename>kexec.target</filename>,
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <filename>local-fs.target</filename>,
ca37bb3c4127b35d333203398bd983ee730d9da5Jan S Berg <filename>local-fs-pre.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>mail-transfer-agent.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>multi-user.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>network.target</filename>,
ab4ab2edaac480f68b476dc19e015c54cd4f1978Lubos Kosco <filename>nss-lookup.target</filename>,
ab4ab2edaac480f68b476dc19e015c54cd4f1978Lubos Kosco <filename>nss-user-lookup.target</filename>,
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <filename>poweroff.target</filename>,
f9fd2b96d1c5ea62664f74da0e34a04b6511a8ffLubos Kosco <filename>printer.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>reboot.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>remote-fs.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>remote-fs-pre.target</filename>,
4bb936310d8f131aa850821e9254ac14242c7f95Knut Anders Hatlen <filename>rescue.target</filename>,
4bb936310d8f131aa850821e9254ac14242c7f95Knut Anders Hatlen <filename>rpcbind.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>runlevel2.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>runlevel3.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>runlevel4.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>runlevel5.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>shutdown.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>sigpwr.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>sleep.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>smartcard.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>sockets.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>sound.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>suspend.target</filename>,
87396bac3204b6788c817e19222626eefde8f3f0Knut Anders Hatlen <filename>swap.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>sysinit.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>syslog.service</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>syslog.socket</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>syslog.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>time-sync.target</filename>,
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <filename>umount.target</filename></para>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye </refsynopsisdiv>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye
6d7c6f82e644c205bc679ee5b1fa2929ec949963Lubos Kosco <refsect1>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <title>Description</title>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <para>A few units are treated specially by
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye systemd. They have special internal semantics and
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye cannot be renamed.</para>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye </refsect1>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye
c1f3e4e0a112250b8f94dde7b94a87a6a2d864b8Lubos Kosco <refsect1>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <title>Special System Units</title>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye
25fddb6fbc2130e3847315ff2b0b6819ff3feccaLubos Kosco <variablelist>
67b14513c549ae0027ba7590e736b3dd3281db7cLubos Kosco <varlistentry>
67b14513c549ae0027ba7590e736b3dd3281db7cLubos Kosco <term><filename>basic.target</filename></term>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <listitem>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <para>A special target unit
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye covering early boot-up.</para>
a1318a82916028f363b3c5b52e7fd7256b632497Trond Norbye <para>systemd automatically
adds dependencies of the types
Requires and After for this
target unit to all SysV
service units configured for
runlevel 1 to 5.</para>
<para>Usually this should pull-in
all sockets, mount points,
swap devices and other basic
initialization necessary for
the general purpose
daemons. Most normal daemons
should have dependencies of
type After and Requires on
this unit.</para>
</listitem>
</varlistentry>
<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>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>ctrl-alt-del.target</filename></term>
<listitem>
<para>systemd starts this
target whenever
Control+Alt+Del is pressed on
the console. Usually this
should be aliased (symlinked)
to
<filename>reboot.target</filename>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>cryptsetup.target</filename></term>
<listitem>
<para>A target that pulls in
setup services for all
encrypted block
devices.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>dbus.service</filename></term>
<listitem>
<para>A special unit for the
D-Bus system bus. As soon as
this service is fully started
up systemd will connect to it
and register its
service.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>dbus.socket</filename></term>
<listitem>
<para>A special unit for the
D-Bus system bus socket. All
units with
<literal>Type=dbus</literal>
automatically gain a
dependency on this
unit.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>default.target</filename></term>
<listitem>
<para>The default unit systemd
starts at bootup. Usually this
should be aliased (symlinked)
to
<filename>multi-user.target</filename>
or
<filename>graphical.target</filename>.</para>
<para>The default unit systemd
starts at bootup can be
overridden with the
<varname>systemd.unit=</varname>
kernel command line option.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>display-manager.service</filename></term>
<listitem>
<para>The display manager
service. Usually this should
be aliased (symlinked) to
<filename>gdm.service</filename>
or a similar display manager
service.</para>
<para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
units with a LSB header
referring to the
<literal>$x-display-manager</literal>
facility, for compatibility
with Debian.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>emergency.target</filename></term>
<listitem>
<para>A special target unit
that starts an emergency
shell on the main
console. This unit is supposed
to be used with the kernel
command line option
<varname>systemd.unit=</varname>
and has otherwise little use.
</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 all 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 login shall add
Wants dependencies for their
unit to this unit (or
<filename>multi-user.target</filename>)
during installation.</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>http-daemon.target</filename></term>
<listitem>
<para>A target for pulling in
an HTTP server if there is
any.</para>
<para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
units with a LSB header
referring to the
<literal>$httpd</literal>
facility.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>halt.target</filename></term>
<listitem>
<para>A special target unit
for shutting down and halting the system.</para>
<para>Applications wanting to
halt the system should start
this unit.</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>systemd automatically
adds dependencies of type
After to all mount units that
refer to local mount points
for this target unit. In
addition, systemd adds
dependencies of type Wants to
this target unit for those
mounts listed in
<filename>/etc/fstab</filename>
that have the
<option>auto</option> and
<option>comment=systemd.mount</option>
mount options set.</para>
<para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
units with an LSB header
referring to the
<literal>$local_fs</literal>
facility.</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>mail-transfer-agent.target</filename></term>
<listitem>
<para>The mail transfer agent
(MTA) service. Usually this
should pull-in all units
necessary for
sending/receiving mails on the
local host.</para>
<para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
units with an LSB header
referring to the
<literal>$mail-transfer-agent</literal>
or
<literal>$mail-transport-agent</literal>
facilities, for compatibility
with Debian.</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 Wants dependencies to
this unit for their unit during
installation.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>network.target</filename></term>
<listitem>
<para>systemd automatically
adds dependencies of type
After 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>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. systemd
automatically adds
dependencies of type After 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. </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>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>
</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
After 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>remote-fs-pre.target</filename></term>
<listitem>
<para>This target unit is
automatically ordered before
all remote mount points marked
with <option>auto</option>
(see above). It can be used to
execute certain units before
all remote mounts.</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>rpcbind.target</filename></term>
<listitem>
<para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
units with an LSB header
referring to the
<literal>$rpcbind</literal>
facility.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>runlevel2.target</filename></term>
<listitem>
<para>This is a target that is
called whenever the SysV
compatibility code asks for
runlevel 2. It is a good idea
to make this an alias for
(i.e. symlink to)
<filename>multi-user.target</filename>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>runlevel3.target</filename></term>
<listitem>
<para>This is a target that is
called whenever the SysV
compatibility code asks for
runlevel 3. It is a good idea
to make this an alias for
(i.e. symlink to)
<filename>multi-user.target</filename>
or
<filename>graphical.target</filename>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>runlevel4.target</filename></term>
<listitem>
<para>This is a target that is
called whenever the SysV
compatibility code asks for
runlevel 4. It is a good idea
to make this an alias for
(i.e. symlink to)
<filename>multi-user.target</filename>
or
<filename>graphical.target</filename>.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>runlevel5.target</filename></term>
<listitem>
<para>This is a target that is
called whenever the SysV
compatibility code asks for
runlevel 5. It is a good idea
to make this an alias for
(i.e. symlink to)
<filename>multi-user.target</filename>
or
<filename>graphical.target</filename>.</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 Conflicts
dependencies to this unit for
their service unit, which is
implicitly done when
<varname>DefaultDependencies=yes</varname>
is set (the default).</para>
<para>systemd automatically
adds dependencies of type
Conflicts to this target unit
for all SysV init script
service units that shall be
terminated in SysV runlevels 0
or 6.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>sigpwr.target</filename></term>
<listitem>
<para>A special target that is
started when systemd receives
the SIGPWR process signal,
which is normally sent by the
kernel or UPS daemons when
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>
and
<filename>hibernate.target</filename>
and may be used to hook units
into the sleep state
logic.</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>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>sockets.target</filename></term>
<listitem>
<para>A special target unit
that sets up all service
sockets.</para>
<para>Services that can be
socket-activated shall add
Wants dependencies to this
unit for their socket unit
during installation.</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>
</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>A special target unit
covering early boot-up scripts.</para>
<para>systemd automatically
adds dependencies of the types
Wants and After for all
SysV service units configured
for runlevels that are not 0
to 6 to this target unit.
This covers the special
boot-up runlevels some
distributions have, such as S
or b.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>syslog.service</filename></term>
<listitem>
<para>The syslog service if
any. Implementations should
create a symlink from the
actual syslog implementation
to this generic name for
activating it.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>syslog.socket</filename></term>
<listitem>
<para>The socket unit where
syslog implementations should
listen on. All userspace log
messages will be made
available on this
socket.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>syslog.target</filename></term>
<listitem>
<para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
units with an LSB header
referring to the
<literal>$syslog</literal>
facility.</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>time-sync.target</filename></term>
<listitem>
<para>systemd automatically
adds dependencies of type
After 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>
<varlistentry>
<term><filename>umount.target</filename></term>
<listitem>
<para>A special target unit
that umounts 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 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>default.target</filename>,
<filename>shutdown.target</filename>,
<filename>sockets.target</filename></para>
<para>In addition the following special unit is
understood only when systemd runs as service instance:</para>
<variablelist>
<varlistentry>
<term><filename>exit.service</filename></term>
<listitem>
<para>A special service unit
for shutting down the
user service manager.</para>
<para>Applications wanting to
terminate the user service
manager should start this
unit. If systemd receives
SIGTERM or SIGINT when running
as user service daemon it will
start this unit.</para>
<para>Normally, this pulls in
<filename>shutdown.target</filename>
which in turn should be
conflicted by all units that
want to be shut down on
user service manager exit.</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>bootup</refentrytitle><manvolnum>7</manvolnum></citerefentry>
</para>
</refsect1>
</refentry>