X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsystemd.special.xml.in;h=49dc3892c0c4bc67c8e4a41cf9b6d85f82b49477;hb=707e5e52804a8f041f0d2f822f0bcf7062ad24ac;hp=1c9e88c612d0401fe6086af4c9e6af3c8e7febb5;hpb=a1b256b0b562481404bda8304e04dee7d7d5e7c9;p=elogind.git diff --git a/man/systemd.special.xml.in b/man/systemd.special.xml.in index 1c9e88c61..49dc3892c 100644 --- a/man/systemd.special.xml.in +++ b/man/systemd.special.xml.in @@ -50,6 +50,8 @@ basic.target, ctrl-alt-del.target, + @SPECIAL_DBUS_SERVICE@, + dbus.target, default.target, display-manager.service, emergency.service, @@ -68,17 +70,16 @@ 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, @@ -109,16 +110,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 +133,39 @@ reboot.target. + + @SPECIAL_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 + @SPECIAL_DBUS_SERVICE@ + (or a socket unit that + activates this + service). + + default.target @@ -156,14 +189,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 @@ -236,8 +269,8 @@ mounts listed in /etc/fstab that have the - auto and - comment=systemd.mount + and + mount options set. systemd automatically @@ -255,7 +288,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 +434,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 +488,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 @@ -551,6 +545,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