system/systemd
system/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd synced 2024-07-21 18:24:38 +00:00
Code Issues Actions 5 Packages Projects Releases Wiki Activity

docs: Update section about XDG autostart generator

Browse source 
The generator is already merged. So update the corresponding section to
describe the current status.
This commit is contained in:
Benjamin Berg 2020-07-20 10:45:48 +02:00 committed by Zbigniew Jędrzejewski-Szmek
parent e6791b5522
commit 6a097936b2
1 changed files with 11 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
docs/DESKTOP_ENVIRONMENTS.md
View file

@ -91,16 +91,18 @@ global default for all (graphical) applications.
## XDG autostart integration
To allow XDG autostart integration, systemd will ship a cross-desktop generator
to create appropriate units for the autostart directory.
Desktop Environments will be able to make use of this simply by starting the
appropriate XDG related targets (representing e.g. content of the
`$XDG_CURRENT_DESKTOP` environment variable to handle `OnlyShowIn/NotShowIn`).
The names and ordering rules for these targets are to be defined.
To allow XDG autostart integration, systemd ships a cross-desktop generator
to create appropriate units for the autostart directory
(`systemd-xdg-autostart-generator`).
Desktop Environments can opt-in to using this by starting
`xdg-desktop-autostart.target`. The systemd generator correctly handles
`OnlyShowIn=` and `NotShowin=`. It also handles the KDE and GNOME specific
`X-KDE-autostart-condition=` and `AutostartCondition=` by using desktop
environment provided binaries in an `ExecCondition=` line.
This generator will likely never support certain desktop specific extensions.
One such example is the GNOME specific feature to bind a service to a settings
variable.
However, this generator is somewhat limited in what it supports. For example,
all generated units will have `After=graphical-session.target` set on them,
it may therefore not be useful to start session services.
## Startup and shutdown best practices