X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsystemd.special.xml.in;h=afe882e51f231638b21eb5074ca374cb40a84b31;hp=1c9e88c612d0401fe6086af4c9e6af3c8e7febb5;hb=591622d7efbc828f00f190d91b6608148b967ff5;hpb=a1b256b0b562481404bda8304e04dee7d7d5e7c9 diff --git a/man/systemd.special.xml.in b/man/systemd.special.xml.in index 1c9e88c61..afe882e51 100644 --- a/man/systemd.special.xml.in +++ b/man/systemd.special.xml.in @@ -50,9 +50,11 @@ 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, @@ -68,22 +70,22 @@ rescue.target, rpcbind.target, rtc-set.target, - runlevel0.target, - runlevel1.target, runlevel2.target, runlevel3.target, runlevel4.target, runlevel5.target, - runlevel6.target shutdown.target, sigpwr.target, 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 @@ -109,16 +111,15 @@ target unit to all SysV service units configured for runlevel 1 to 5. - systemd automatically - adds dependencies of the types - Wants and After for all - SysV service units configured - for runlevels that are not 0 - to 6 to this target unit. - This covers the special - boot-up runlevels some - distributions have, such as S - or b. + Usually this should pull-in + all sockets, mount points, + swap devices and other basic + initialization necessary for + the general purpose + daemons. Most normal daemons + should have dependencies of + type After and Requires on + this unit. @@ -133,6 +134,39 @@ reboot.target. + + dbus.service + + A special unit for the + D-Bus system bus. As soon as + this service is fully started + 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). + + default.target @@ -156,14 +190,14 @@ The display manager service. Usually this should be aliased (symlinked) to - gdm.service + xdm.service or a similar display manager service. systemd automatically adds dependencies of type After for this target unit to all SysV init script service - units with an LSB header + units with a LSB header referring to the $x-display-manager facility, for compatibility @@ -171,9 +205,9 @@ - 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 @@ -236,8 +270,8 @@ mounts listed in /etc/fstab that have the - auto and - comment=systemd.mount + and + mount options set. systemd automatically @@ -255,7 +289,7 @@ The mail transfer agent (MTA) service. Usually this - should pull in all units + should pull-in all units necessary for sending/receiving mails on the local host. @@ -401,32 +435,6 @@ facility. - - runlevel0.target - - This is a target that is - called whever the SysV - compatibility code asks for - runlevel 0. This is an alias - for - poweroff.target, - for compatibility with - SysV. - - - - runlevel1.target - - This is a target that is - called whever the SysV - compatibility code asks for - runlevel 1. This is an alias - for - rescue.target, - for compatibility with - SysV. - - runlevel2.target @@ -481,19 +489,6 @@ graphical.target. - - runlevel6.target - - This is a target that is - called whever the SysV - compatibility code asks for - runlevel 6. This is an alias - for - reboot.target, - for compatibility with - SysV. - - shutdown.target @@ -505,8 +500,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 @@ -551,6 +548,44 @@ files. + + sysinit.target + + A special target unit + covering early boot-up scripts. + systemd automatically + adds dependencies of the types + Wants and After for all + SysV service units configured + for runlevels that are not 0 + to 6 to this target unit. + This covers the special + boot-up runlevels some + distributions have, such as S + 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 @@ -621,13 +656,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, @@ -646,22 +719,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. @@ -670,9 +743,9 @@ See Also - systemd.unit5 - systemd.service5 - systemd.socket5 + systemd.unit5, + systemd.service5, + systemd.socket5, systemd.target5