[PATCH 1/5] activation: change SystemdService to ActivationRequest

Simon McVittie simon.mcvittie at collabora.co.uk
Mon Jan 3 02:52:17 PST 2011

On Sun, 02 Jan 2011 at 22:46:53 +0000, Scott James Remnant wrote:
> Instead of hardcoding the request string to be the systemd service
> name, make it any string you wish to pass to the activation manager.

How does this work for activatable services not provided by the distro (i.e.
from source)? If I'm writing a service uk.co.collabora.lolcatkit and I don't
know whether my users will be using Upstart or systemd, it looks as though
I'll have to choose between these two:

option 1: conventional config for systemd, unconventional config for Upstart

- ActivationRequest=lolcatkit
- define a systemd unit called "lolcatkit"
- define an arbitrarily-named Upstart job with
  "start on dbus-activation lolcatkit", even though lolcatkit isn't actually
  a well-known bus name

option 2: unconventional config for systemd, conventional config for Upstart

- ActivationRequest=uk.co.collabora.lolcatkit (or just omit it)
- define a systemd unit called uk.co.collabora.lolcatkit, even though systemd
  units conventionally have short names (much like sysvinit init scripts)
- define an arbitrarily-named Upstart job with
  "start on dbus-activation uk.co.collabora.lolcatkit"

(I vaguely suspect that we'll end up with some sort of best-practice convention
that Upstart jobs for D-Bus services are named after either the bus name, or
the same short name you'd use for the systemd unit / the init script / etc.)


More information about the dbus mailing list