mirrors/systemd
0
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-24 09:33:32 +08:00
Code Issues Packages Projects Releases Wiki Activity
ce1dde29b9
systemd/man/systemd.special.xml

1165 lines
65 KiB
XML
Raw Normal View History

man: document a few special units
2010-05-17 04:45:11 +08:00
<?xml version='1.0'?> <!--*-nxml-*-->
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!--
This file is part of systemd.
Copyright 2010 Lennart Poettering
systemd is free software; you can redistribute it and/or modify it
relicense to LGPLv2.1 (with exceptions) We finally got the OK from all contributors with non-trivial commits to relicense systemd from GPL2+ to LGPL2.1+. Some udev bits continue to be GPL2+ for now, but we are looking into relicensing them too, to allow free copy/paste of all code within systemd. The bits that used to be MIT continue to be MIT. The big benefit of the relicensing is that closed source code may now link against libsystemd-login.so and friends.
2012-04-12 06:20:58 +08:00
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
man: document a few special units
2010-05-17 04:45:11 +08:00
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
relicense to LGPLv2.1 (with exceptions) We finally got the OK from all contributors with non-trivial commits to relicense systemd from GPL2+ to LGPL2.1+. Some udev bits continue to be GPL2+ for now, but we are looking into relicensing them too, to allow free copy/paste of all code within systemd. The bits that used to be MIT continue to be MIT. The big benefit of the relicensing is that closed source code may now link against libsystemd-login.so and friends.
2012-04-12 06:20:58 +08:00
Lesser General Public License for more details.
man: document a few special units
2010-05-17 04:45:11 +08:00
relicense to LGPLv2.1 (with exceptions) We finally got the OK from all contributors with non-trivial commits to relicense systemd from GPL2+ to LGPL2.1+. Some udev bits continue to be GPL2+ for now, but we are looking into relicensing them too, to allow free copy/paste of all code within systemd. The bits that used to be MIT continue to be MIT. The big benefit of the relicensing is that closed source code may now link against libsystemd-login.so and friends.
2012-04-12 06:20:58 +08:00
You should have received a copy of the GNU Lesser General Public License
man: document a few special units
2010-05-17 04:45:11 +08:00
along with systemd; If not, see <http://www.gnu.org/licenses/>.
-->
<refentry id="systemd.special">
<refentryinfo>
<title>systemd.special</title>
<productname>systemd</productname>
<authorgroup>
<author>
<contrib>Developer</contrib>
<firstname>Lennart</firstname>
<surname>Poettering</surname>
<email>lennart@poettering.net</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta>
<refentrytitle>systemd.special</refentrytitle>
<manvolnum>7</manvolnum>
</refmeta>
<refnamediv>
<refname>systemd.special</refname>
man: update documentation of special units
2012-04-04 04:32:05 +08:00
<refpurpose>Special systemd units</refpurpose>
man: document a few special units
2010-05-17 04:45:11 +08:00
</refnamediv>
<refsynopsisdiv>
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<para><filename>basic.target</filename>,
units: introduce new Documentation= field and make use of it everywhere This should help making the boot process a bit easier to explore and understand for the administrator. The simple idea is that "systemctl status" now shows a link to documentation alongside the other status and decriptionary information of a service. This patch adds the necessary fields to all our shipped units if we have proper documentation for them.
2012-05-21 21:12:18 +08:00
<filename>bluetooth.target</filename>,
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<filename>ctrl-alt-del.target</filename>,
units: introduce new Documentation= field and make use of it everywhere This should help making the boot process a bit easier to explore and understand for the administrator. The simple idea is that "systemctl status" now shows a link to documentation alongside the other status and decriptionary information of a service. This patch adds the necessary fields to all our shipped units if we have proper documentation for them.
2012-05-21 21:12:18 +08:00
<filename>cryptsetup.target</filename>,
cryptsetup: introduce new cryptsetup-pre.traget unit so that services can make sure they are started before and stopped after any LUKS setup https://bugzilla.redhat.com/show_bug.cgi?id=1097938
2014-06-18 06:07:56 +08:00
<filename>cryptsetup-pre.target</filename>,
build-sys: drop special name hack for dbus.service since a native service file is now shipped upstream dbus
2010-07-10 06:22:38 +08:00
<filename>dbus.service</filename>,
man: update documentation of special units
2012-04-04 04:32:05 +08:00
<filename>dbus.socket</filename>,
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<filename>default.target</filename>,
unit: turn display-manager.target into a service
2010-05-25 04:29:59 +08:00
<filename>display-manager.service</filename>,
units: introduce emergency.target
2010-07-13 05:49:20 +08:00
<filename>emergency.target</filename>,
units: rename halt/hibernate/kexec/poweroff/reboot/suspend to systed-xxx These service units also execute our own code, hence rename the accordingly and prefix them with systemd-
2012-06-25 20:24:56 +08:00
<filename>exit.target</filename>,
<filename>final.target</filename>,
units: introduce new Documentation= field and make use of it everywhere This should help making the boot process a bit easier to explore and understand for the administrator. The simple idea is that "systemctl status" now shows a link to documentation alongside the other status and decriptionary information of a service. This patch adds the necessary fields to all our shipped units if we have proper documentation for them.
2012-05-21 21:12:18 +08:00
<filename>getty.target</filename>,
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<filename>graphical.target</filename>,
service: drop special HTTP server target, as it is a bad idea anf Fedora specific This was premarily intended to support the LSB facility $httpd which is only known by Fedora, and a bad idea since it lacks any real-life usecase. Similar, drop support for some other old Fedora-specific facilities. Also, document the rules for introduction of new facilities, to clarify the situation for the future.
2012-10-31 09:55:04 +08:00
<filename>halt.target</filename>,
sleep: implement suspend/hibernate as first class targets
2012-05-05 08:06:58 +08:00
<filename>hibernate.target</filename>,
logind: support for hybrid sleep (i.e. suspend+hibernate at the same time)
2012-10-28 06:49:04 +08:00
<filename>hybrid-sleep.target</filename>,
add initrd-fs.target and root-fs.target Instead of using local-fs*.target in the initrd, use root-fs.target for sysroot.mount and initrd-fs.target for /sysroot/usr and friends. Using local-fs.target would mean to carry over the activated local-fs.target to the isolated initrd-switch-root.target and thus in the real root. Having local-fs.target already active after deserialization causes ordering problems with the real root services and targets. We better isolate to targets for initrd-switch-root.target, which are only available in the initrd.
2013-03-05 02:01:05 +08:00
<filename>initrd-fs.target</filename>,
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<filename>kbrequest.target</filename>,
man: update documentation of special units
2012-04-04 04:32:05 +08:00
<filename>kexec.target</filename>,
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<filename>local-fs.target</filename>,
units: introduce local-fs-pre.target and remote-fs-pre.target This hook target enables services to order themselves between network.target and remote mounts, which is needed for GFS2 and similar systems.
2011-10-11 09:33:53 +08:00
<filename>local-fs-pre.target</filename>,
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<filename>multi-user.target</filename>,
<filename>network.target</filename>,
unit: replace remote-fs-setup.target by network-online.target https://bugzilla.redhat.com/show_bug.cgi?id=787314
2013-03-29 04:18:58 +08:00
<filename>network-online.target</filename>,
units: introduce network-pre.target as place to hook in firewalls network-pre.target is a passive target that should be pulled in by services that want to be executed before any network is configured (for example: firewall scrips). network-pre.target should be ordered before all network managemet services (but not be pulled in by them). network-pre.target should be order after all services that want to be executed before any network is configured (and be pulled in by them).
2014-06-11 17:33:02 +08:00
<filename>network-pre.target</filename>,
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<filename>nss-lookup.target</filename>,
units: introduce new Documentation= field and make use of it everywhere This should help making the boot process a bit easier to explore and understand for the administrator. The simple idea is that "systemctl status" now shows a link to documentation alongside the other status and decriptionary information of a service. This patch adds the necessary fields to all our shipped units if we have proper documentation for them.
2012-05-21 21:12:18 +08:00
<filename>nss-user-lookup.target</filename>,
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<filename>paths.target</filename>,
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<filename>poweroff.target</filename>,
units: introduce new Documentation= field and make use of it everywhere This should help making the boot process a bit easier to explore and understand for the administrator. The simple idea is that "systemctl status" now shows a link to documentation alongside the other status and decriptionary information of a service. This patch adds the necessary fields to all our shipped units if we have proper documentation for them.
2012-05-21 21:12:18 +08:00
<filename>printer.target</filename>,
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<filename>reboot.target</filename>,
<filename>remote-fs.target</filename>,
units: introduce local-fs-pre.target and remote-fs-pre.target This hook target enables services to order themselves between network.target and remote mounts, which is needed for GFS2 and similar systems.
2011-10-11 09:33:53 +08:00
<filename>remote-fs-pre.target</filename>,
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<filename>rescue.target</filename>,
Make initrd.target the default target in the initrd First, rename root-fs.target to initrd-root-fs.target to clarify its usage. Mount units with "x-initrd-rootfs.mount" are now ordered before initrd-root-fs.target. As we sometimes construct /sysroot mounts in /etc/fstab in the initrd, we want these to be mounted before the initrd-root-fs.target is active. initrd.target can be the default target in the initrd. (normal startup) : : v basic.target | ______________________/| / | | sysroot.mount | | | v | initrd-root-fs.target | | | v | initrd-parse-etc.service (custom initrd services) | | v | (sysroot-usr.mount and | various mounts marked | with fstab option | x-initrd.mount) | | | v | initrd-fs.target | | \______________________ | \| v initrd.target | v initrd-cleanup.service isolates to initrd-switch-root.target | v ______________________/| / | | initrd-udevadm-cleanup-db.service | | (custom initrd services) | | | \______________________ | \| v initrd-switch-root.target | v initrd-switch-root.service | v switch-root
2013-03-14 20:12:10 +08:00
<filename>initrd-root-fs.target</filename>,
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<filename>rpcbind.target</filename>,
<filename>runlevel2.target</filename>,
<filename>runlevel3.target</filename>,
<filename>runlevel4.target</filename>,
<filename>runlevel5.target</filename>,
<filename>shutdown.target</filename>,
<filename>sigpwr.target</filename>,
sleep: implement suspend/hibernate as first class targets
2012-05-05 08:06:58 +08:00
<filename>sleep.target</filename>,
units: introduce new Documentation= field and make use of it everywhere This should help making the boot process a bit easier to explore and understand for the administrator. The simple idea is that "systemctl status" now shows a link to documentation alongside the other status and decriptionary information of a service. This patch adds the necessary fields to all our shipped units if we have proper documentation for them.
2012-05-21 21:12:18 +08:00
<filename>smartcard.target</filename>,
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<filename>sockets.target</filename>,
units: introduce new Documentation= field and make use of it everywhere This should help making the boot process a bit easier to explore and understand for the administrator. The simple idea is that "systemctl status" now shows a link to documentation alongside the other status and decriptionary information of a service. This patch adds the necessary fields to all our shipped units if we have proper documentation for them.
2012-05-21 21:12:18 +08:00
<filename>sound.target</filename>,
sleep: implement suspend/hibernate as first class targets
2012-05-05 08:06:58 +08:00
<filename>suspend.target</filename>,
man: replace syslog name in man page by configured name
2010-05-18 04:45:52 +08:00
<filename>swap.target</filename>,
units: introduce and explain sysinit.target
2010-06-05 00:43:40 +08:00
<filename>sysinit.target</filename>,
man: update documentation of special units
2012-04-04 04:32:05 +08:00
<filename>syslog.socket</filename>,
man: document systemd-update-generator
2012-06-27 21:12:29 +08:00
<filename>system-update.target</filename>,
man: Sort the entries in systemd.special(7) This manpage presents the special targets in alphabetical order, but time-sync.target appeared in the wrong place.
2011-08-07 07:04:38 +08:00
<filename>time-sync.target</filename>,
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<filename>timers.target</filename>,
man: document four basic slices
2013-07-10 13:33:13 +08:00
<filename>umount.target</filename>,
<filename>-.slice</filename>,
<filename>system.slice</filename>,
<filename>user.slice</filename>,
<filename>machine.slice</filename></para>
man: document a few special units
2010-05-17 04:45:11 +08:00
</refsynopsisdiv>
<refsect1>
<title>Description</title>
<para>A few units are treated specially by
systemd. They have special internal semantics and
cannot be renamed.</para>
</refsect1>
<refsect1>
<title>Special System Units</title>
<variablelist>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<varlistentry>
<term><filename>basic.target</filename></term>
<listitem>
<para>A special target unit
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
covering basic boot-up.</para>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<para>systemd automatically
adds dependencies of the types
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<varname>Requires=</varname>
and <varname>After=</varname>
for this target unit to all
services (except for those
with
<varname>DefaultDependencies=no</varname>).</para>
<para>Usually this should
pull-in all mount points, swap
devices, sockets, timers, and
path units and other basic
units: introduce and explain sysinit.target
2010-06-05 00:43:40 +08:00
initialization necessary for
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
general purpose
daemons.</para>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
</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>
units: introduce new Documentation= field and make use of it everywhere This should help making the boot process a bit easier to explore and understand for the administrator. The simple idea is that "systemctl status" now shows a link to documentation alongside the other status and decriptionary information of a service. This patch adds the necessary fields to all our shipped units if we have proper documentation for them.
2012-05-21 21:12:18 +08:00
<varlistentry>
<term><filename>cryptsetup.target</filename></term>
<listitem>
<para>A target that pulls in
setup services for all
encrypted block
devices.</para>
</listitem>
</varlistentry>
man: document syslog and dbus services
2010-05-25 04:31:50 +08:00
<varlistentry>
build-sys: drop special name hack for dbus.service since a native service file is now shipped upstream dbus
2010-07-10 06:22:38 +08:00
<term><filename>dbus.service</filename></term>
man: document syslog and dbus services
2010-05-25 04:31:50 +08:00
<listitem>
<para>A special unit for the
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
D-Bus bus daemon. As soon as
man: document syslog and dbus services
2010-05-25 04:31:50 +08:00
this service is fully started
up systemd will connect to it
and register its
service.</para>
</listitem>
</varlistentry>
man: update documentation of special units
2012-04-04 04:32:05 +08:00
<varlistentry>
<term><filename>dbus.socket</filename></term>
<listitem>
<para>A special unit for the
D-Bus system bus socket. All
units with
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<varname>Type=dbus</varname>
man: update documentation of special units
2012-04-04 04:32:05 +08:00
automatically gain a
dependency on this
unit.</para>
</listitem>
</varlistentry>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<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>
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<para>The default unit systemd
starts at bootup can be
man: Spelling fixes
2011-04-24 03:55:24 +08:00
overridden with the
man: fix references to systemd.unit= on the kernel cmdline https://bugs.freedesktop.org/show_bug.cgi?id=35720
2011-03-29 05:39:18 +08:00
<varname>systemd.unit=</varname>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
kernel command line option.</para>
</listitem>
</varlistentry>
unit: turn display-manager.target into a service
2010-05-25 04:29:59 +08:00
<varlistentry>
<term><filename>display-manager.service</filename></term>
<listitem>
<para>The display manager
service. Usually this should
be aliased (symlinked) to
man: update documentation of special units
2012-04-04 04:32:05 +08:00
<filename>gdm.service</filename>
unit: turn display-manager.target into a service
2010-05-25 04:29:59 +08:00
or a similar display manager
service.</para>
</listitem>
</varlistentry>
man: document a few special units
2010-05-17 04:45:11 +08:00
<varlistentry>
units: introduce emergency.target
2010-07-13 05:49:20 +08:00
<term><filename>emergency.target</filename></term>
man: document a few special units
2010-05-17 04:45:11 +08:00
<listitem>
units: introduce emergency.target
2010-07-13 05:49:20 +08:00
<para>A special target unit
man: document a few special units
2010-05-17 04:45:11 +08:00
that starts an emergency
shell on the main
console. This unit is supposed
to be used with the kernel
command line option
man: fix references to systemd.unit= on the kernel cmdline https://bugs.freedesktop.org/show_bug.cgi?id=35720
2011-03-29 05:39:18 +08:00
<varname>systemd.unit=</varname>
man: document a few special units
2010-05-17 04:45:11 +08:00
and has otherwise little use.
</para>
</listitem>
</varlistentry>
man: update documentation of special units
2012-04-04 04:32:05 +08:00
<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>
units: introduce new Documentation= field and make use of it everywhere This should help making the boot process a bit easier to explore and understand for the administrator. The simple idea is that "systemctl status" now shows a link to documentation alongside the other status and decriptionary information of a service. This patch adds the necessary fields to all our shipped units if we have proper documentation for them.
2012-05-21 21:12:18 +08:00
<varlistentry>
<term><filename>getty.target</filename></term>
<listitem>
<para>A special target unit
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
that pulls in statically
configured local TTY
<filename>getty</filename>
instances.
units: introduce new Documentation= field and make use of it everywhere This should help making the boot process a bit easier to explore and understand for the administrator. The simple idea is that "systemctl status" now shows a link to documentation alongside the other status and decriptionary information of a service. This patch adds the necessary fields to all our shipped units if we have proper documentation for them.
2012-05-21 21:12:18 +08:00
</para>
</listitem>
</varlistentry>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<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
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
for graphical logins shall add
<varname>Wants=</varname>
dependencies for their unit to
this unit (or
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<filename>multi-user.target</filename>)
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
during installation. This is
best configured via
<varname>WantedBy=graphical.target</varname>
in the unit's
<literal>[Install]</literal>
section.</para>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
</listitem>
</varlistentry>
sleep: implement suspend/hibernate as first class targets
2012-05-05 08:06:58 +08:00
<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>
logind: support for hybrid sleep (i.e. suspend+hibernate at the same time)
2012-10-28 06:49:04 +08:00
<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>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<varlistentry>
<term><filename>halt.target</filename></term>
<listitem>
<para>A special target unit
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
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>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<para>Applications wanting to
halt the system should start
this unit.</para>
</listitem>
</varlistentry>
add initrd-fs.target and root-fs.target Instead of using local-fs*.target in the initrd, use root-fs.target for sysroot.mount and initrd-fs.target for /sysroot/usr and friends. Using local-fs.target would mean to carry over the activated local-fs.target to the isolated initrd-switch-root.target and thus in the real root. Having local-fs.target already active after deserialization causes ordering problems with the real root services and targets. We better isolate to targets for initrd-switch-root.target, which are only available in the initrd.
2013-03-05 02:01:05 +08:00
<varlistentry>
<term><filename>initrd-fs.target</filename></term>
<listitem>
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<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>
man: add sd_j_open_files to return values section
2013-06-14 11:32:15 +08:00
and all mount points found in
add initrd-fs.target and root-fs.target Instead of using local-fs*.target in the initrd, use root-fs.target for sysroot.mount and initrd-fs.target for /sysroot/usr and friends. Using local-fs.target would mean to carry over the activated local-fs.target to the isolated initrd-switch-root.target and thus in the real root. Having local-fs.target already active after deserialization causes ordering problems with the real root services and targets. We better isolate to targets for initrd-switch-root.target, which are only available in the initrd.
2013-03-05 02:01:05 +08:00
<filename>/etc/fstab</filename>
man: mention x-initrd.mount option in fstab options list
2014-06-30 21:41:01 +08:00
that have
add initrd-fs.target and root-fs.target Instead of using local-fs*.target in the initrd, use root-fs.target for sysroot.mount and initrd-fs.target for /sysroot/usr and friends. Using local-fs.target would mean to carry over the activated local-fs.target to the isolated initrd-switch-root.target and thus in the real root. Having local-fs.target already active after deserialization causes ordering problems with the real root services and targets. We better isolate to targets for initrd-switch-root.target, which are only available in the initrd.
2013-03-05 02:01:05 +08:00
<option>x-initrd.mount</option>
man: mention x-initrd.mount option in fstab options list
2014-06-30 21:41:01 +08:00
and not have <option>noauto</option>
mount options set.</para>
add initrd-fs.target and root-fs.target Instead of using local-fs*.target in the initrd, use root-fs.target for sysroot.mount and initrd-fs.target for /sysroot/usr and friends. Using local-fs.target would mean to carry over the activated local-fs.target to the isolated initrd-switch-root.target and thus in the real root. Having local-fs.target already active after deserialization causes ordering problems with the real root services and targets. We better isolate to targets for initrd-switch-root.target, which are only available in the initrd.
2013-03-05 02:01:05 +08:00
</listitem>
</varlistentry>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<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>
man: update documentation of special units
2012-04-04 04:32:05 +08:00
<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>
man: document a few special units
2010-05-17 04:45:11 +08:00
<varlistentry>
<term><filename>local-fs.target</filename></term>
<listitem>
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<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
man: document a few special units
2010-05-17 04:45:11 +08:00
adds dependencies of type
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<varname>Wants=</varname> to
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
this target unit for those
mounts listed in
man: document a few special units
2010-05-17 04:45:11 +08:00
<filename>/etc/fstab</filename>
that have the
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<option>auto</option> mount
option set.</para>
man: document a few special units
2010-05-17 04:45:11 +08:00
</listitem>
</varlistentry>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<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
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
add <varname>Wants=</varname>
dependencies for their unit to
this unit during
installation. This is best
configured via
man: fix typo https://bugs.freedesktop.org/show_bug.cgi?id=68723
2013-09-06 19:14:26 +08:00
<varname>WantedBy=multi-user.target</varname>
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
in the unit's
<literal>[Install]</literal>
section.</para>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
</listitem>
</varlistentry>
unit: replace remote-fs-setup.target by network-online.target https://bugzilla.redhat.com/show_bug.cgi?id=787314
2013-03-29 04:18:58 +08:00
<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
man: wording and grammar updates This includes regularly-submitted corrections to comma setting and orthographical mishaps that appeared in man/ in recent commits. In this particular commit: - the usual comma fixes - expand contractions (this is prose)
2013-08-25 15:01:45 +08:00
generally do not need to pull
unit: replace remote-fs-setup.target by network-online.target https://bugzilla.redhat.com/show_bug.cgi?id=787314
2013-03-29 04:18:58 +08:00
this in.</para>
</listitem>
</varlistentry>
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<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>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<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>
man: document a few special units
2010-05-17 04:45:11 +08:00
<varlistentry>
<term><filename>remote-fs.target</filename></term>
<listitem>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<para>Similar to
<filename>local-fs.target</filename>,
but for remote mount
points.</para>
man: document a few special units
2010-05-17 04:45:11 +08:00
<para>systemd automatically
adds dependencies of type
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<varname>After=</varname> for
this target unit to all SysV
init script service units with
an LSB header referring to the
man: fix minor typo
2010-05-25 00:58:43 +08:00
<literal>$remote_fs</literal>
man: document a few special units
2010-05-17 04:45:11 +08:00
facility.</para>
</listitem>
</varlistentry>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<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>
add initrd-fs.target and root-fs.target Instead of using local-fs*.target in the initrd, use root-fs.target for sysroot.mount and initrd-fs.target for /sysroot/usr and friends. Using local-fs.target would mean to carry over the activated local-fs.target to the isolated initrd-switch-root.target and thus in the real root. Having local-fs.target already active after deserialization causes ordering problems with the real root services and targets. We better isolate to targets for initrd-switch-root.target, which are only available in the initrd.
2013-03-05 02:01:05 +08:00
<varlistentry>
Make initrd.target the default target in the initrd First, rename root-fs.target to initrd-root-fs.target to clarify its usage. Mount units with "x-initrd-rootfs.mount" are now ordered before initrd-root-fs.target. As we sometimes construct /sysroot mounts in /etc/fstab in the initrd, we want these to be mounted before the initrd-root-fs.target is active. initrd.target can be the default target in the initrd. (normal startup) : : v basic.target | ______________________/| / | | sysroot.mount | | | v | initrd-root-fs.target | | | v | initrd-parse-etc.service (custom initrd services) | | v | (sysroot-usr.mount and | various mounts marked | with fstab option | x-initrd.mount) | | | v | initrd-fs.target | | \______________________ | \| v initrd.target | v initrd-cleanup.service isolates to initrd-switch-root.target | v ______________________/| / | | initrd-udevadm-cleanup-db.service | | (custom initrd services) | | | \______________________ | \| v initrd-switch-root.target | v initrd-switch-root.service | v switch-root
2013-03-14 20:12:10 +08:00
<term><filename>initrd-root-fs.target</filename></term>
add initrd-fs.target and root-fs.target Instead of using local-fs*.target in the initrd, use root-fs.target for sysroot.mount and initrd-fs.target for /sysroot/usr and friends. Using local-fs.target would mean to carry over the activated local-fs.target to the isolated initrd-switch-root.target and thus in the real root. Having local-fs.target already active after deserialization causes ordering problems with the real root services and targets. We better isolate to targets for initrd-switch-root.target, which are only available in the initrd.
2013-03-05 02:01:05 +08:00
<listitem>
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<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.
add initrd-fs.target and root-fs.target Instead of using local-fs*.target in the initrd, use root-fs.target for sysroot.mount and initrd-fs.target for /sysroot/usr and friends. Using local-fs.target would mean to carry over the activated local-fs.target to the isolated initrd-switch-root.target and thus in the real root. Having local-fs.target already active after deserialization causes ordering problems with the real root services and targets. We better isolate to targets for initrd-switch-root.target, which are only available in the initrd.
2013-03-05 02:01:05 +08:00
</para>
</listitem>
</varlistentry>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<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>
service: drop special HTTP server target, as it is a bad idea anf Fedora specific This was premarily intended to support the LSB facility $httpd which is only known by Fedora, and a bad idea since it lacks any real-life usecase. Similar, drop support for some other old Fedora-specific facilities. Also, document the rules for introduction of new facilities, to clarify the situation for the future.
2012-10-31 09:55:04 +08:00
<para>These are targets that
are called whenever the SysV
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
compatibility code asks for
service: drop special HTTP server target, as it is a bad idea anf Fedora specific This was premarily intended to support the LSB facility $httpd which is only known by Fedora, and a bad idea since it lacks any real-life usecase. Similar, drop support for some other old Fedora-specific facilities. Also, document the rules for introduction of new facilities, to clarify the situation for the future.
2012-10-31 09:55:04 +08:00
runlevel 2, 3, 4, 5,
respectively. It is a good
idea to make this an alias for
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
(i.e. symlink to)
<filename>multi-user.target</filename>
service: drop special HTTP server target, as it is a bad idea anf Fedora specific This was premarily intended to support the LSB facility $httpd which is only known by Fedora, and a bad idea since it lacks any real-life usecase. Similar, drop support for some other old Fedora-specific facilities. Also, document the rules for introduction of new facilities, to clarify the situation for the future.
2012-10-31 09:55:04 +08:00
(for runlevel 2) or
<filename>graphical.target</filename>
(the others).</para>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
</listitem>
</varlistentry>
man: document a few special units
2010-05-17 04:45:11 +08:00
<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
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
shall add <varname>Conflicts=</varname>
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
dependencies to this unit for
unit: introduce IgnoreDependencyFailure=
2010-07-12 08:56:17 +08:00
their service unit, which is
implicitly done when
<varname>DefaultDependencies=yes</varname>
is set (the default).</para>
man: document a few special units
2010-05-17 04:45:11 +08:00
</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
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
kernel or UPS daemons when
man: document a few special units
2010-05-17 04:45:11 +08:00
power fails.</para>
</listitem>
</varlistentry>
sleep: implement suspend/hibernate as first class targets
2012-05-05 08:06:58 +08:00
<varlistentry>
<term><filename>sleep.target</filename></term>
<listitem>
<para>A special target unit
that is pulled in by
logind: support for hybrid sleep (i.e. suspend+hibernate at the same time)
2012-10-28 06:49:04 +08:00
<filename>suspend.target</filename>,
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<filename>hibernate.target</filename>
and
<filename>hybrid-sleep.target</filename>
sleep: implement suspend/hibernate as first class targets
2012-05-05 08:06:58 +08:00
and may be used to hook units
into the sleep state
logic.</para>
</listitem>
</varlistentry>
man: document a few special units
2010-05-17 04:45:11 +08:00
<varlistentry>
<term><filename>sockets.target</filename></term>
<listitem>
<para>A special target unit
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
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>
man: document a few special units
2010-05-17 04:45:11 +08:00
<para>Services that can be
socket-activated shall add
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<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>
man: document a few special units
2010-05-17 04:45:11 +08:00
</listitem>
</varlistentry>
sleep: implement suspend/hibernate as first class targets
2012-05-05 08:06:58 +08:00
<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>
man: document a few special units
2010-05-17 04:45:11 +08:00
<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>
units: introduce and explain sysinit.target
2010-06-05 00:43:40 +08:00
<varlistentry>
<term><filename>sysinit.target</filename></term>
<listitem>
<para>A special target unit
covering early boot-up scripts.</para>
</listitem>
</varlistentry>
man: update documentation of special units
2012-04-04 04:32:05 +08:00
<varlistentry>
<term><filename>syslog.socket</filename></term>
<listitem>
man: typo fixes Fixes a few more typos. Also changes a "Accept=no" to "Accept=false" to be consistent with the previous examples in the same man page.
2012-11-02 06:35:34 +08:00
<para>The socket unit
man: update documentation of special units
2012-04-04 04:32:05 +08:00
syslog implementations should
listen on. All userspace log
messages will be made
man: add various links from man pages to appropriate wiki pages
2012-06-29 00:58:56 +08:00
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>
man: update documentation of special units
2012-04-04 04:32:05 +08:00
</listitem>
</varlistentry>
man: document systemd-update-generator
2012-06-27 21:12:29 +08:00
<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>
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<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>
unit: introduce IgnoreDependencyFailure=
2010-07-12 08:56:17 +08:00
<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>
man: document systemd-update-generator
2012-06-27 21:12:29 +08:00
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
</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
man: fix typos in systemd.special
2013-05-06 22:32:23 +08:00
in smartcard management
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
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
man: fix typos in systemd.special
2013-05-06 22:32:23 +08:00
dynamically when audio
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
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
doc: update punctuation Resolve spotted issues related to missing or extraneous commas, dashes.
2014-02-17 10:37:13 +08:00
specifically that these <emphasis>passive</emphasis>
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
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>
man: document that the passive units cannot be pulled in mnaully
2013-03-26 22:16:50 +08:00
<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>
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
<variablelist>
cryptsetup: introduce new cryptsetup-pre.traget unit so that services can make sure they are started before and stopped after any LUKS setup https://bugzilla.redhat.com/show_bug.cgi?id=1097938
2014-06-18 06:07:56 +08:00
<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
doc: grammatical corrections
2014-06-28 06:48:28 +08:00
start-up order between units,
cryptsetup: introduce new cryptsetup-pre.traget unit so that services can make sure they are started before and stopped after any LUKS setup https://bugzilla.redhat.com/show_bug.cgi?id=1097938
2014-06-18 06:07:56 +08:00
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>
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
<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>
man: network.target is also a passive target
2013-03-27 09:49:50 +08:00
<varlistentry>
<term><filename>network.target</filename></term>
<listitem>
unit: replace remote-fs-setup.target by network-online.target https://bugzilla.redhat.com/show_bug.cgi?id=787314
2013-03-29 04:18:58 +08:00
<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
man: updates to the passive target section
2014-06-11 00:52:28 +08:00
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
unit: replace remote-fs-setup.target by network-online.target https://bugzilla.redhat.com/show_bug.cgi?id=787314
2013-03-29 04:18:58 +08:00
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>
man: network.target is also a passive target
2013-03-27 09:49:50 +08:00
<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>
units: introduce network-pre.target as place to hook in firewalls network-pre.target is a passive target that should be pulled in by services that want to be executed before any network is configured (for example: firewall scrips). network-pre.target should be ordered before all network managemet services (but not be pulled in by them). network-pre.target should be order after all services that want to be executed before any network is configured (and be pulled in by them).
2014-06-11 17:33:02 +08:00
<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>
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
<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>
man: updates to the passive target section
2014-06-11 00:52:28 +08:00
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
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
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>
man: updates to the passive target section
2014-06-11 00:52:28 +08:00
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>
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
</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
man: wording and grammar updates This is a recurring submission and includes corrections to various issue spotted. I guess I can just skip over reporting ubiquitous comma placement fixes… Highligts in this particular commit: - the "unsigned" type qualifier is completed to form a full type "unsigned int" - alphabetic -> lexicographic (that way we automatically define how numbers get sorted)
2013-09-13 03:12:49 +08:00
remote mount showing up, it
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
should use
units: fix some left-over mentions of remote-fs-setup.target
2013-04-10 01:05:49 +08:00
<filename>network-online.target</filename>
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
(see above).</para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>rpcbind.target</filename></term>
<listitem>
man: updates to the passive target section
2014-06-11 00:52:28 +08:00
<para>The portmapper/rpcbind
pulls in this target and
orders itself before it, to
indicate its
availability. systemd
automatically adds
dependencies of type
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
<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>
man: updates to the passive target section
2014-06-11 00:52:28 +08:00
<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
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
<varname>After=</varname> for
this target unit to all SysV
init script service units with
an LSB header referring to the
<literal>$time</literal>
man: updates to the passive target section
2014-06-11 00:52:28 +08:00
facility. </para>
man: rearrange systemd.special(7) to clarify which units are passive and which ones aren't This also adds a short explanation paragraph for this.
2013-03-26 05:30:51 +08:00
</listitem>
</varlistentry>
man: document a few special units
2010-05-17 04:45:11 +08:00
</variablelist>
</refsect1>
<refsect1>
drop support for MANAGER_SESSION, introduce MANAGER_USER instead
2010-11-16 05:12:41 +08:00
<title>Special User Units</title>
man: document a few special units
2010-05-17 04:45:11 +08:00
drop support for MANAGER_SESSION, introduce MANAGER_USER instead
2010-11-16 05:12:41 +08:00
<para>When systemd runs as a user instance, the
man: document a few special units
2010-05-17 04:45:11 +08:00
following special units are available, which have
similar definitions as their system counterparts:
man: complete service.special(7) man page
2010-05-18 01:37:21 +08:00
<filename>default.target</filename>,
man: document a few special units
2010-05-17 04:45:11 +08:00
<filename>shutdown.target</filename>,
man: properly document the system targets that are also available for the user instance
2013-03-26 05:32:59 +08:00
<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>
unit: introduce exit.service for exiting from session instances
2010-05-25 04:31:38 +08:00
man: improvements to comma placement This is a recurring submission and includes corrections to: comma placement.
2013-12-26 09:47:44 +08:00
<para>In addition, the following special unit is
unit: introduce exit.service for exiting from session instances
2010-05-25 04:31:38 +08:00
understood only when systemd runs as service instance:</para>
<variablelist>
<varlistentry>
units: rename halt/hibernate/kexec/poweroff/reboot/suspend to systed-xxx These service units also execute our own code, hence rename the accordingly and prefix them with systemd-
2012-06-25 20:24:56 +08:00
<term><filename>exit.target</filename></term>
unit: introduce exit.service for exiting from session instances
2010-05-25 04:31:38 +08:00
<listitem>
<para>A special service unit
for shutting down the
drop support for MANAGER_SESSION, introduce MANAGER_USER instead
2010-11-16 05:12:41 +08:00
user service manager.</para>
unit: introduce exit.service for exiting from session instances
2010-05-25 04:31:38 +08:00
<para>Applications wanting to
drop support for MANAGER_SESSION, introduce MANAGER_USER instead
2010-11-16 05:12:41 +08:00
terminate the user service
manager should start this
unit. If systemd receives
man: add more formatting markup
2013-06-30 00:09:14 +08:00
<constant>SIGTERM</constant> or <constant>SIGINT</constant> when running
man: wording and grammar updates This is a recurring submission and includes corrections to various issue spotted. I guess I can just skip over reporting ubiquitous comma placement fixes… Highligts in this particular commit: - the "unsigned" type qualifier is completed to form a full type "unsigned int" - alphabetic -> lexicographic (that way we automatically define how numbers get sorted)
2013-09-13 03:12:49 +08:00
as user service daemon, it will
drop support for MANAGER_SESSION, introduce MANAGER_USER instead
2010-11-16 05:12:41 +08:00
start this unit.</para>
unit: introduce exit.service for exiting from session instances
2010-05-25 04:31:38 +08:00
<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
drop support for MANAGER_SESSION, introduce MANAGER_USER instead
2010-11-16 05:12:41 +08:00
user service manager exit.</para>
unit: introduce exit.service for exiting from session instances
2010-05-25 04:31:38 +08:00
</listitem>
</varlistentry>
</variablelist>
man: document a few special units
2010-05-17 04:45:11 +08:00
</refsect1>
man: document four basic slices
2013-07-10 13:33:13 +08:00
<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
man: document Slice= setting (and other fixes)
2013-07-19 10:10:06 +08:00
root of the hierarchy. It
usually does not contain units
directly, but may be used to
set defaults for the whole
tree.</para>
man: document four basic slices
2013-07-10 13:33:13 +08:00
</listitem>
</varlistentry>
<varlistentry>
<term><filename>system.slice</filename></term>
<listitem>
man: wording and grammar updates This includes regularly-submitted corrections to comma setting and orthographical mishaps that appeared in man/ in recent commits.
2013-07-21 12:53:14 +08:00
<para>By default, all services
man: document four basic slices
2013-07-10 13:33:13 +08:00
services started by
man: document Slice= setting (and other fixes)
2013-07-19 10:10:06 +08:00
<command>systemd</command> are
found in this slice.</para>
man: document four basic slices
2013-07-10 13:33:13 +08:00
</listitem>
</varlistentry>
<varlistentry>
<term><filename>user.slice</filename></term>
<listitem>
man: wording and grammar updates This includes regularly-submitted corrections to comma setting and orthographical mishaps that appeared in man/ in recent commits.
2013-07-21 12:53:14 +08:00
<para>By default, all user
man: document four basic slices
2013-07-10 13:33:13 +08:00
processes and services started
on behalf of the user,
including the per-user systemd
man: document Slice= setting (and other fixes)
2013-07-19 10:10:06 +08:00
instance are found in this
slice.</para>
man: document four basic slices
2013-07-10 13:33:13 +08:00
</listitem>
</varlistentry>
<varlistentry>
<term><filename>machine.slice</filename></term>
<listitem>
man: fix typo
2014-06-19 16:43:03 +08:00
<para>By default, all virtual
man: document Slice= setting (and other fixes)
2013-07-19 10:10:06 +08:00
machines and containers
registered with
<command>systemd-machined</command>
are found in this slice.
man: document four basic slices
2013-07-10 13:33:13 +08:00
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
man: document a few special units
2010-05-17 04:45:11 +08:00
<refsect1>
<title>See Also</title>
<para>
man: update documentation of special units
2012-04-04 04:32:05 +08:00
<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
man: document new shutdown features
2010-08-16 21:56:42 +08:00
<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>,
man: introduce bootup(7)
2012-06-23 05:14:19 +08:00
<citerefentry><refentrytitle>systemd.target</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
man: document four basic slices
2013-07-10 13:33:13 +08:00
<citerefentry><refentrytitle>systemd.slice</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
units: introduce new timers.target and paths.target to hook timer/path units into for boot
2013-03-26 04:20:08 +08:00
<citerefentry><refentrytitle>bootup</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
add initrd-fs.target and root-fs.target Instead of using local-fs*.target in the initrd, use root-fs.target for sysroot.mount and initrd-fs.target for /sysroot/usr and friends. Using local-fs.target would mean to carry over the activated local-fs.target to the isolated initrd-switch-root.target and thus in the real root. Having local-fs.target already active after deserialization causes ordering problems with the real root services and targets. We better isolate to targets for initrd-switch-root.target, which are only available in the initrd.
2013-03-05 02:01:05 +08:00
<citerefentry><refentrytitle>systemd-fstab-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>
man: document a few special units
2010-05-17 04:45:11 +08:00
</para>
</refsect1>
</refentry>
Reference in New Issue Copy Permalink