adds dependencies of the types
Requires and After for this
service units configured for
<
para>Usually this should pull-in
all sockets, mount points,
swap devices and other basic
initialization necessary for
daemons. Most normal daemons
should have dependencies of
type After and Requires on
<
para>This target is started
automatically as soon as a
available at boot.</
para>
<
para>systemd starts this
Control+Alt+Del is pressed on
the console. Usually this
should be aliased (symlinked)
<
para>A target that pulls in
<
para>A special unit for the
D-Bus system bus. As soon as
this service is fully started
up systemd will connect to it
<
para>A special unit for the
D-Bus system bus socket. All
<
literal>Type=dbus</
literal>
<
para>The default unit systemd
starts at bootup. Usually this
should be aliased (symlinked)
<
para>The default unit systemd
kernel command line option.</
para>
<
para>The display manager
service. Usually this should
be aliased (symlinked) to
or a similar display manager
<
para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
<
literal>$x-display-manager</
literal>
facility, for compatibility
<
para>A special target unit
console. This unit is supposed
to be used with the kernel
and has otherwise little use.
<
para>A special target unit
shutdown logic and may be used
to pull in late services after
already terminated and all
<
para>A special target unit
that pulls in all local TTY
<
filename>getty</
filename> instances.
<
para>A special target unit
for setting up a graphical
login screen. This pulls in
<
para>Units that are needed
for graphical login shall add
Wants dependencies for their
during installation.</
para>
<
para>A special target unit
<
para>A target for pulling in
an HTTP server if there is
<
para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
<
literal>$httpd</
literal>
<
para>A special target unit
for shutting down and halting the system.</
para>
<
para>Applications wanting to
halt the system should start
<
para>systemd starts this
target whenever Alt+ArrowUp is
pressed on the console. This
is a good candidate to be
<
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
<
para>systemd automatically
adds dependencies of type
After to all mount units that
refer to local mount points
dependencies of type Wants to
this target unit for those
<
option>auto</
option> and
mount options set.</
para>
<
para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
<
literal>$local_fs</
literal>
<
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
<
para>The mail transfer agent
(MTA) service. Usually this
<
para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
<
literal>$mail-transfer-agent</
literal>
<
literal>$mail-transport-agent</
literal>
facilities, for compatibility
<
para>A special target unit
for setting up a multi-user
system (non-graphical). This
<
para>Units that are needed
for a multi-user system shall
add Wants dependencies to
this unit for their unit during
<
para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
<
literal>$network</
literal>
<
para>A target that should be
used as synchronization point
service lookups. Note that
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>
<
para>A target that should be
used as synchronization point
service lookups. Note that
<
para>A special target unit
for shutting down and powering off the system.</
para>
<
para>Applications wanting to
power off the system should start
is an alias for this target
unit, for compatibility with SysV.</
para>
<
para>This target is started
automatically as soon as a
<
para>A special target unit
for shutting down and rebooting the system.</
para>
<
para>Applications wanting to
reboot the system should start
is an alias for this target
unit, for compatibility with SysV.</
para>
<
para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
<
literal>$remote_fs</
literal>
<
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>
<
para>A special target unit
for setting up the base system
and a rescue shell.</
para>
is an alias for this target
unit, for compatibility with SysV.</
para>
<
para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
<
literal>$rpcbind</
literal>
<
para>This is a target that is
compatibility code asks for
runlevel 2. It is a good idea
to make this an alias for
<
para>This is a target that is
compatibility code asks for
runlevel 3. It is a good idea
to make this an alias for
<
para>This is a target that is
compatibility code asks for
runlevel 4. It is a good idea
to make this an alias for
<
para>This is a target that is
compatibility code asks for
runlevel 5. It is a good idea
to make this an alias for
<
para>A special target unit
that terminates the services
on system shutdown.</
para>
<
para>Services that shall be
terminated on system shutdown
dependencies to this unit for
their service unit, which is
<
varname>DefaultDependencies=yes</
varname>
is set (the default).</
para>
<
para>systemd automatically
adds dependencies of type
Conflicts to this target unit
service units that shall be
terminated in SysV runlevels 0
<
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
<
para>A special target unit
and may be used to hook units
<
para>This target is started
automatically as soon as a
available at boot.</
para>
<
para>A special target unit
<
para>Services that can be
socket-activated shall add
Wants dependencies to this
unit for their socket unit
during installation.</
para>
<
para>This target is started
automatically as soon as a
sound card is plugged in or
<
para>A special target unit
<
para>A special target unit
covering early boot-up scripts.</
para>
<
para>systemd automatically
adds dependencies of the types
SysV service units configured
for runlevels that are not 0
to 6 to this target unit.
distributions have, such as S
<
para>The syslog service if
any. Implementations should
create a symlink from the
actual syslog implementation
<
para>The socket unit where
syslog implementations should
listen on. All userspace log
<
para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
<
literal>$syslog</
literal>
<
para>systemd automatically
adds dependencies of type
After for this target unit to
all SysV init script service
<
para>A special target unit
that umounts all mount and
automount points on system
<
para>Mounts that shall be
unmounted on system shutdown
dependencies to this unit for
their mount unit, which is
<
varname>DefaultDependencies=yes</
varname>
is set (the default).</
para>
<
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:
<
para>In addition the following special unit is
understood only when systemd runs as service instance:</
para>
<
para>A special service unit
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
<
para>Normally, this pulls in
conflicted by all units that
user service manager exit.</
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>