X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.special.xml.in;h=218754051e945831a36c9b9981290d9edf60d07a;hb=d418f857f87f3f381f52f6ee17f2fad6e36aca86;hp=2855f6a25f807d2c2353a8d119172d79fa683372;hpb=5dc50792ac1bc627bf9b50d259b4e7546b3f8d86;p=elogind.git
diff --git a/man/systemd.special.xml.in b/man/systemd.special.xml.in
index 2855f6a25..218754051 100644
--- a/man/systemd.special.xml.in
+++ b/man/systemd.special.xml.in
@@ -51,7 +51,6 @@
basic.target,
ctrl-alt-del.target,
dbus.service,
- dbus.target,
default.target,
display-manager.service,
emergency.target,
@@ -69,7 +68,6 @@
remote-fs.target,
rescue.target,
rpcbind.target,
- rtc-set.target,
runlevel2.target,
runlevel3.target,
runlevel4.target,
@@ -79,12 +77,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-stdout-syslog-bridge.service,
+ systemd-stdout-syslog-bridge.socket,
+ time-sync.target,
umount.target
@@ -143,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,8 +155,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.
@@ -213,7 +189,7 @@
console. This unit is supposed
to be used with the kernel
command line option
- systemd.default=
+ systemd.unit=
and has otherwise little use.
@@ -300,7 +276,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
@@ -422,24 +398,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.target
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
@@ -451,7 +414,7 @@
runlevel3.target
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
@@ -465,7 +428,7 @@
runlevel4.target
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
@@ -479,7 +442,7 @@
runlevel5.target
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
@@ -565,27 +528,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
@@ -597,15 +539,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).
@@ -630,7 +563,7 @@
- systemd-logger.service
+ systemd-stdout-syslog-bridge.service
This is internally used
by systemd to provide syslog
@@ -638,15 +571,15 @@
maintains.
This is a
socket-activated service, see
- system-logger.socket.
+ system-stdout-syslog-bridge.socket.
- systemd-logger.socket
+ systemd-stdout-syslog-bridge.socket
Socket 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
@@ -676,6 +609,19 @@
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
@@ -698,9 +644,9 @@
- 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,
@@ -719,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.