From: Lennart Poettering Date: Thu, 30 Mar 2017 09:54:45 +0000 (+0200) Subject: man: use for all unit entries X-Git-Tag: v234~345^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=b493bdafa951b35e33919bdc7f81da3b0e210a0d;p=thirdparty%2Fsystemd.git man: use for all unit entries So far, all sections of the systemd.special(7) man page used for listing the targets, with one exception: the "Special Passive User Units" one. Let's clean this up and use the same formatting everywhere. --- diff --git a/man/systemd.special.xml b/man/systemd.special.xml index fa3dc1c5d44..66c45e39a3c 100644 --- a/man/systemd.special.xml +++ b/man/systemd.special.xml @@ -901,64 +901,58 @@ Special Passive User Units - - graphical-session.target - - This target is active whenever any graphical session is running. It - is used to stop user services which only apply to a graphical (X, - Wayland, etc.) session when the session is terminated. Such services - should have PartOf=graphical-session.target in their - [Unit] section. A target for a particular session - (e. g. gnome-session.target) starts and stops - graphical-session.target with - BindsTo=graphical-session.target. - - Which services are started by a session target is determined by the - Wants= and Requires= dependencies. - For services that can be enabled independently, symlinks in - .wants/ and .requires/ should be - used, see - systemd.unit5. - Those symlinks should either be shipped in packages, or should be added - dynamically after installation, for example using systemctl add-wants, see - systemctl1. - + + + graphical-session.target + + This target is active whenever any graphical session is running. It is used to stop user services which + only apply to a graphical (X, Wayland, etc.) session when the session is terminated. Such services should + have PartOf=graphical-session.target in their [Unit] section. A target + for a particular session (e. g. gnome-session.target) starts and stops + graphical-session.target with BindsTo=graphical-session.target. + + Which services are started by a session target is determined by the Wants= and + Requires= dependencies. For services that can be enabled independently, symlinks in + .wants/ and .requires/ should be used, see + systemd.unit5. Those + symlinks should either be shipped in packages, or should be added dynamically after installation, for example + using systemctl add-wants, see + systemctl1. + - - Nautilus as part of a GNOME session + + Nautilus as part of a GNOME session - gnome-session.target pulls in Nautilus as - top-level service: + gnome-session.target pulls in Nautilus as top-level service: - [Unit] + [Unit] Description=User systemd services for GNOME graphical session Wants=nautilus.service -BindsTo=graphical-session.target - +BindsTo=graphical-session.target - nautilus.service gets stopped when the session stops: + nautilus.service gets stopped when the session stops: - [Unit] + [Unit] Description=Render the desktop icons with Nautilus PartOf=graphical-session.target [Service] -… - - - - - - graphical-session-pre.target - - This target contains services which set up the environment or - global configuration of a graphical session, such as SSH/GPG agents - (which need to export an environment variable into all desktop processes) - or migration of obsolete d-conf keys after an OS upgrade (which needs to - happen before starting any process that might use them). This target must - be started before starting a graphical session - like gnome-session.target. - +… + + + + + + graphical-session-pre.target + + This target contains services which set up the environment or global configuration of a graphical + session, such as SSH/GPG agents (which need to export an environment variable into all desktop processes) or + migration of obsolete d-conf keys after an OS upgrade (which needs to happen before starting any process that + might use them). This target must be started before starting a graphical session like + gnome-session.target. + + +