<filename>halt.target</filename>,
<filename>kbrequest.target</filename>,
<filename>local-fs.target</filename>,
+ <filename>local-fs-pre.target</filename>,
<filename>mail-transfer-agent.target</filename>,
<filename>multi-user.target</filename>,
<filename>network.target</filename>,
<filename>poweroff.target</filename>,
<filename>reboot.target</filename>,
<filename>remote-fs.target</filename>,
+ <filename>remote-fs-pre.target</filename>,
<filename>rescue.target</filename>,
<filename>rpcbind.target</filename>,
- <filename>rtc-set.target</filename>,
<filename>runlevel2.target</filename>,
<filename>runlevel3.target</filename>,
<filename>runlevel4.target</filename>,
<filename>sockets.target</filename>,
<filename>swap.target</filename>,
<filename>sysinit.target</filename>,
- <filename>@SPECIAL_SYSLOG_SERVICE@</filename>,
<filename>syslog.target</filename>,
<filename>systemd-initctl.service</filename>,
<filename>systemd-initctl.socket</filename>,
- <filename>systemd-logger.service</filename>,
- <filename>systemd-logger.socket</filename>,
+ <filename>systemd-stdout-syslog-bridge.service</filename>,
+ <filename>systemd-stdout-syslog-bridge.socket</filename>,
+ <filename>time-sync.target</filename>,
<filename>umount.target</filename></para>
</refsynopsisdiv>
<filename>graphical.target</filename>.</para>
<para>The default unit systemd
starts at bootup can be
- overriden with the
- <varname>systemd.default=</varname>
+ overridden with the
+ <varname>systemd.unit=</varname>
kernel command line option.</para>
</listitem>
</varlistentry>
console. This unit is supposed
to be used with the kernel
command line option
- <varname>systemd.default=</varname>
+ <varname>systemd.unit=</varname>
and has otherwise little use.
</para>
</listitem>
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>
all SysV init script service
units with an LSB header
referring to the
- <literal>$mail-transfer-argent</literal>
+ <literal>$mail-transfer-agent</literal>
or
<literal>$mail-transport-agent</literal>
facilities, for compatibility
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>
facility.</para>
</listitem>
</varlistentry>
- <varlistentry>
- <term><filename>rtc-set.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>runlevel2.target</filename></term>
<listitem>
<para>This is a target that is
- called whever the SysV
+ called whenever the SysV
compatibility code asks for
runlevel 2. It is a good idea
to make this an alias for
<term><filename>runlevel3.target</filename></term>
<listitem>
<para>This is a target that is
- called whever the SysV
+ called whenever the SysV
compatibility code asks for
runlevel 3. It is a good idea
to make this an alias for
<term><filename>runlevel4.target</filename></term>
<listitem>
<para>This is a target that is
- called whever the SysV
+ called whenever the SysV
compatibility code asks for
runlevel 4. It is a good idea
to make this an alias for
<term><filename>runlevel5.target</filename></term>
<listitem>
<para>This is a target that is
- called whever the SysV
+ called whenever the SysV
compatibility code asks for
runlevel 5. It is a good idea
to make this an alias for
or b.</para>
</listitem>
</varlistentry>
- <varlistentry>
- <term><filename>@SPECIAL_SYSLOG_SERVICE@</filename></term>
- <listitem>
- <para>A special unit for the
- syslog daemon. As soon as
- this service is fully started
- up systemd will connect to it
- and use it for logging if it
- has been configured for
- that.</para>
-
- <para>Units should generally
- avoid depending on this unit
- directly and instead refer to
- the
- <filename>syslog.target</filename>
- unit instead, which pulls this
- one in directly or indirectly
- via socket-based activation.</para>
- </listitem>
- </varlistentry>
<varlistentry>
<term><filename>syslog.target</filename></term>
<listitem>
referring to the
<literal>$syslog</literal>
facility.</para>
-
- <para>Administrators should
- ensure that this target pulls
- in a service unit with the
- name or alias of
- <filename>@SPECIAL_SYSLOG_SERVICE@</filename>
- (or a socket unit that
- activates this
- service).</para>
</listitem>
</varlistentry>
<varlistentry>
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>systemd-logger.service</filename></term>
+ <term><filename>systemd-stdout-syslog-bridge.service</filename></term>
<listitem>
<para>This is internally used
by systemd to provide syslog
maintains.</para>
<para>This is a
socket-activated service, see
- <filename>system-logger.socket</filename>.</para>
+ <filename>system-stdout-syslog-bridge.socket</filename>.</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><filename>systemd-logger.socket</filename></term>
+ <term><filename>systemd-stdout-syslog-bridge.socket</filename></term>
<listitem>
<para>Socket activation unit
for
- <filename>system-logger.service</filename>. systemd
+ <filename>system-stdout-syslog-bridge.service</filename>. systemd
will automatically add
dependencies of types Requires
and After to all units that
<filename>system-shutdownd.service</filename>.</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>