From c481d8a99961c3f728a46a3d7d9cbef060b77792 Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Wed, 9 Nov 2016 17:52:48 +0000 Subject: [PATCH 3/4] Spec: document systemd activation We didn't say that SystemdService existed. Now we do, together with enough context to make it make sense. Signed-off-by: Simon McVittie --- doc/dbus-specification.xml | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/doc/dbus-specification.xml b/doc/dbus-specification.xml index 5feffa3..2e72c31 100644 --- a/doc/dbus-specification.xml +++ b/doc/dbus-specification.xml @@ -5152,6 +5152,39 @@ property on screen 0 of the display, pointing to this bus. + + + systemd Activation + + + Service description files may contain a + SystemdService key. Its value is the name of a + systemd + service, for example + dbus-com.example.MyDaemon.service. + + + + If this key is present, the bus daemon may carry out activation for + this D-Bus service by sending a request to systemd asking it to + start the systemd service whose name is the value of + SystemdService. For example, the reference + dbus-daemon has a + --systemd-activation option that enables this + feature, and that option is given when it is started by systemd. + + + + On the well-known system bus, it is a common practice to set + SystemdService to dbus-, + followed by the well-known bus name, followed by + .service, then register that name as an alias + for the real systemd service. This allows D-Bus activation of a + service to be enabled or disabled independently of whether the + service is started by systemd during boot. + + -- 2.10.2