X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.special.xml.in;h=804504a8335ae04d9f99241b058858938a06b2fb;hb=9d8677dad260d7dc20146f8affe3d376daff7c19;hp=ac9f0f5a6ab1598cd7d07fba9dd5eec67668dbfa;hpb=83bda35801aa3d7ed180ec374a4bcdfe9dc1a8e4;p=elogind.git
diff --git a/man/systemd.special.xml.in b/man/systemd.special.xml.in
index ac9f0f5a6..804504a83 100644
--- a/man/systemd.special.xml.in
+++ b/man/systemd.special.xml.in
@@ -51,10 +51,9 @@
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,
@@ -79,12 +78,12 @@
sockets.target,
swap.target,
sysinit.target,
- @SPECIAL_SYSLOG_SERVICE@,
syslog.target,
systemd-initctl.service,
systemd-initctl.socket,
systemd-logger.service,
- systemd-logger.socket
+ systemd-logger.socket,
+ umount.target
@@ -142,28 +141,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).
@@ -179,7 +156,7 @@
The default unit systemd
starts at bootup can be
overriden with the
- systemd.default=
+ systemd.unit=
kernel command line option.
@@ -204,15 +181,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.
@@ -499,8 +476,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 +541,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 +552,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).
@@ -653,13 +602,51 @@
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.
+
+
+
+ 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 +665,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 +689,9 @@
See Also
- systemd.unit5
- systemd.service5
- systemd.socket5
+ systemd.unit5,
+ systemd.service5,
+ systemd.socket5,
systemd.target5