summaryrefslogtreecommitdiff
path: root/service/ca.desrt.dconf.service.in
diff options
context:
space:
mode:
authorSimon McVittie <smcv@collabora.com>2020-12-04 11:11:04 +0000
committerSimon McVittie <smcv@debian.org>2020-12-04 11:14:11 +0000
commitfc46e157bd708aa24ee366e027aa7edbaa0c8648 (patch)
tree4b68553e3d6a225b0efa027a876f4a3f4f953f67 /service/ca.desrt.dconf.service.in
parent490421c6a89f918dbb75ae14efb66a1ce1fe1399 (diff)
downloaddconf-fc46e157bd708aa24ee366e027aa7edbaa0c8648.tar.gz
service: Add a systemd unit for D-Bus activationwip/smcv/systemd-unit
On systems using systemd --user and dbus-daemon --session --systemd-activation, this means that dconf is correctly placed in its own cgroup, instead of being part of dbus.service's cgroup. This allows it to be controlled by systemctl --user, have resource limits set and so on. On other systems (in particular those where systemd is not used at all), the SystemdService field is ignored and dbus-daemon will continue to start dconf-service as its own child process ("traditional activation"), making this change harmless to apply. Resolves: https://gitlab.gnome.org/GNOME/dconf/-/issues/24 Signed-off-by: Simon McVittie <smcv@collabora.com>
Diffstat (limited to 'service/ca.desrt.dconf.service.in')
-rw-r--r--service/ca.desrt.dconf.service.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/service/ca.desrt.dconf.service.in b/service/ca.desrt.dconf.service.in
index 369948a..be0b911 100644
--- a/service/ca.desrt.dconf.service.in
+++ b/service/ca.desrt.dconf.service.in
@@ -1,3 +1,4 @@
[D-BUS Service]
Name=ca.desrt.dconf
Exec=@libexecdir@/dconf-service
+SystemdService=dconf.service