.\" -----------------------------------------------------------------.\" * Define some portability stuff.\" -----------------------------------------------------------------.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.\" http://bugs.debian.org/507673.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.ie \n(.g .ds Aq \(aq.el .ds Aq '.\" -----------------------------------------------------------------.\" * set default formatting.\" -----------------------------------------------------------------.\" disable hyphenation.nh.\" disable justification (adjust text to left margin only).ad l.\" -----------------------------------------------------------------.\" * MAIN CONTENT STARTS HERE *.\" -----------------------------------------------------------------.SH "NAME"systemd.target \- Target unit configuration.SH "SYNOPSIS".PP\fItarget\fR\&.target.SH "DESCRIPTION".PPA unit configuration file whose name ends in"\&.target"encodes information about a target unit of systemd, which is used for grouping units and as well\-known synchronization points during start\-up\&..PPThis unit type has no specific options\&. See\fBsystemd.unit\fR(5)for the common options of all unit configuration files\&. The common configuration items are configured in the generic [Unit] and [Install] sections\&. A separate [Target] section does not exist, since no target\-specific options may be configured\&..PPTarget units do not offer any additional functionality on top of the generic functionality provided by units\&. They exist merely to group units via dependencies (useful as boot targets), and to establish standardized names for synchronization points used in dependencies between units\&. Among other things, target units are a more flexible replacement for SysV runlevels in the classic SysV init system\&. (And for compatibility reasons special target units such asrunlevel3\&.targetexist which are used by the SysV runlevel compatibility code in systemd\&. See\fBsystemd.special\fR(7)for details)\&..PPUnless\fIDefaultDependencies=\fRis set to\fBfalse\fR, target units will implicitly complement all configured dependencies of type\fIWants=\fR,\fIRequires=\fR,\fIRequiresOverridable=\fRwith dependencies of type\fIAfter=\fRif the units in question also have\fIDefaultDependencies=true\fR\&..SH "SEE ALSO".PP\fBsystemd\fR(1),\fBsystemctl\fR(8),\fBsystemd.unit\fR(5),\fBsystemd.special\fR(7),\fBsystemd.directives\fR(7)