NOTE: This document is a work-in-progress.
systemd only supports running one graphical session per user at a time. While this might not have always been the case historically, having multiple sessions for one user running at the same time is problematic. The DBus session bus is shared between all the logins, and services that are started must be implicitly assigned to the user’s current graphical session.
In principle it is possible to run a single graphical session across multiple logind seats, and this could be a way to use more than one display per user. When a user logs in to a second seat, the seat resources could be assigned to the existing session, allowing the graphical environment to present it is a single seat. Currently nothing like this is supported or even planned.
allow cross-desktop integration. Furthermore, systemd defines the three base
All units should be placed into one of these slices depending on their purposes:
session.slice: Contains only processes essential to run the user’s graphical session
app.slice: Contains all normal applications that the user is running
background.slice: Useful for low-priority background tasks
The purpose of this grouping is to assign different priorities to the applications. This could e.g. mean reserving memory to session processes, preferentially killing background tasks in out-of-memory situations or assigning different memory/CPU/IO priorities to ensure that the session runs smoothly under load.
TODO: Will there be a default to place units into e.g.
app.slice by default
rather than the root slice?
To ensure cross-desktop compatibility and encourage sharing of good practices, desktop environments should adhere to the following conventions:
.serviceunits instead of
.scopeunits, i.e. allowing systemd to start the process on behalf of the caller, instead of the caller starting the process and letting systemd know about it, is encouraged.
basename(argv)). This name must not contain a
This has the following advantages:
app-<launcher>-prefix means that the unit defaults can be adjusted using desktop environment specific drop-in files.
.desktopfile when available
TODO: Define the name of slices that should be used.
This could be
TODO: Does it really make sense to insert the
<launcher>? In GNOME I am
currently using a drop-in to configure
TimeoutSec=5s. I feel that such a
policy makes sense, but it may make much more sense to just define a
global default for all (graphical) applications.
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
The names and ordering rules for these targets are to be defined.
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.
Question here are:
gnome-session-shutdown.targetthat is run with
replace-irreversiblyconsidered a good practice?