X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.special.xml.in;h=116a43ccfb30798e6570fdeb43df6ac2963c962c;hb=21e557edcc1894ce4eeb70b71ca16e82e95bc0df;hp=ac9f0f5a6ab1598cd7d07fba9dd5eec67668dbfa;hpb=83bda35801aa3d7ed180ec374a4bcdfe9dc1a8e4;p=elogind.git
diff --git a/man/systemd.special.xml.in b/man/systemd.special.xml.in
index ac9f0f5a6..116a43ccf 100644
--- a/man/systemd.special.xml.in
+++ b/man/systemd.special.xml.in
@@ -51,15 +51,15 @@
basic.target,
ctrl-alt-del.target,
dbus.service,
- dbus.target,
default.target,
display-manager.service,
- emergency.service,
+ emergency.target,
exit.service,
graphical.target,
halt.target,
kbrequest.target,
local-fs.target,
+ local-fs-pre.target,
mail-transfer-agent.target,
multi-user.target,
network.target,
@@ -67,9 +67,9 @@
poweroff.target,
reboot.target,
remote-fs.target,
+ remote-fs-pre.target,
rescue.target,
rpcbind.target,
- rtc-set.target,
runlevel2.target,
runlevel3.target,
runlevel4.target,
@@ -79,12 +79,13 @@
sockets.target,
swap.target,
sysinit.target,
- @SPECIAL_SYSLOG_SERVICE@,
syslog.target,
systemd-initctl.service,
systemd-initctl.socket,
- systemd-logger.service,
- systemd-logger.socket
+ systemd-stdout-syslog-bridge.service,
+ systemd-stdout-syslog-bridge.socket,
+ time-sync.target,
+ umount.target
@@ -142,28 +143,6 @@
up systemd will connect to it
and register its
service.
-
- Units should generally
- avoid depending on this unit
- directly and instead refer to
- the
- dbus.target
- unit instead, which pulls this
- one in directly or indirectly
- via socket-based activation.
-
-
-
- dbus.target
-
- Administrators should
- ensure that this target pulls
- in a service unit with the
- name or alias of
- dbus.service
- (or a socket unit that
- activates this
- service).
@@ -178,8 +157,8 @@
graphical.target.
The default unit systemd
starts at bootup can be
- overriden with the
- systemd.default=
+ overridden with the
+ systemd.unit=
kernel command line option.
@@ -204,15 +183,15 @@
- emergency.service
+ emergency.target
- A special service unit
+ 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
- systemd.default=
+ systemd.unit=
and has otherwise little use.
@@ -283,6 +262,18 @@
facility.
+
+ local-fs-pre.target
+
+ This target unit is
+ automatically ordered before
+ all local mount points marked
+ with
+ (see above). It can be used to
+ execute certain units before
+ all local mounts.
+
+ mail-transfer-agent.target
@@ -299,7 +290,7 @@
all SysV init script service
units with an LSB header
referring to the
- $mail-transfer-argent
+ $mail-transfer-agent
or
$mail-transport-agent
facilities, for compatibility
@@ -396,6 +387,18 @@
facility.
+
+ remote-fs-pre.target
+
+ This target unit is
+ automatically ordered before
+ all remote mount points marked
+ with
+ (see above). It can be used to
+ execute certain units before
+ all remote mounts.
+
+ rescue.target
@@ -421,24 +424,11 @@
facility.
-
- rtc-set.target
-
- 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
- $time
- facility.
-
- runlevel2.targetThis 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
@@ -450,7 +440,7 @@
runlevel3.targetThis 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
@@ -464,7 +454,7 @@
runlevel4.targetThis 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
@@ -478,7 +468,7 @@
runlevel5.targetThis 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
@@ -499,8 +489,10 @@
terminated on system shutdown
shall add Conflicts
dependencies to this unit for
- their service unit during
- installation.
+ their service unit, which is
+ implicitly done when
+ DefaultDependencies=yes
+ is set (the default).systemd automatically
adds dependencies of type
@@ -562,27 +554,6 @@
or b.
-
- @SPECIAL_SYSLOG_SERVICE@
-
- 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.
-
- Units should generally
- avoid depending on this unit
- directly and instead refer to
- the
- syslog.target
- unit instead, which pulls this
- one in directly or indirectly
- via socket-based activation.
-
- syslog.target
@@ -594,15 +565,6 @@
referring to the
$syslog
facility.
-
- Administrators should
- ensure that this target pulls
- in a service unit with the
- name or alias of
- @SPECIAL_SYSLOG_SERVICE@
- (or a socket unit that
- activates this
- service).
@@ -627,7 +589,7 @@
- systemd-logger.service
+ systemd-stdout-syslog-bridge.serviceThis is internally used
by systemd to provide syslog
@@ -635,15 +597,15 @@
maintains.This is a
socket-activated service, see
- system-logger.socket.
+ system-stdout-syslog-bridge.socket.
- systemd-logger.socket
+ systemd-stdout-syslog-bridge.socketSocket activation unit
for
- system-logger.service. systemd
+ system-stdout-syslog-bridge.service. systemd
will automatically add
dependencies of types Requires
and After to all units that
@@ -653,13 +615,64 @@
kernel log buffer.
+
+ systemd-shutdownd.service
+
+ This is internally used
+ by
+ shutdown8
+ to implement delayed shutdowns.
+ This is a
+ socket-activated service, see
+ system-shutdownd.socket.
+
+
+
+ systemd-shutdownd.socket
+
+ Socket activation unit
+ for
+ system-shutdownd.service.
+
+
+
+ time-sync.target
+
+ 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
+ $time
+ facility.
+
+
+
+ umount.target
+
+ A special target unit
+ that umounts all mount and
+ automount points on system
+ shutdown.
+
+ Mounts that shall be
+ unmounted on system shutdown
+ shall add Conflicts
+ dependencies to this unit for
+ their mount unit, which is
+ implicitly done when
+ DefaultDependencies=yes
+ is set (the default).
+
+
- Special Session Units
+ Special User Units
- When systemd runs as a service instance, the
+ When systemd runs as a user instance, the
following special units are available, which have
similar definitions as their system counterparts:
default.target,
@@ -678,22 +691,22 @@
A special service unit
for shutting down the
- session.
+ user service manager.Applications wanting to
- terminate the session should
- start this unit. If systemd
- receives SIGTERM or SIGINT
- when running as session daemon
- it will start this
- unit.
+ 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.Normally, this pulls in
shutdown.target
which in turn should be
conflicted by all units that
want to be shut down on
- session exit.
+ user service manager exit.
@@ -702,9 +715,9 @@
See Also
- systemd.unit5
- systemd.service5
- systemd.socket5
+ systemd.unit5,
+ systemd.service5,
+ systemd.socket5,
systemd.target5