[RFC] Common activation manager via external manager
mzqohf at 0pointer.de
Mon Jan 3 14:06:55 PST 2011
On Mon, 03.01.11 21:51, Scott James Remnant (scott at netsplit.com) wrote:
> On Mon, Jan 3, 2011 at 8:28 PM, Lennart Poettering <mzqohf at 0pointer.de> wrote:
> > On Sun, 02.01.11 22:46, Scott James Remnant (scott at netsplit.com) wrote:
> >> In addition to allow activation of the session bus, the activation
> >> environment is included as well.
> > Again, this is a bad idea: if anybody uses this it is really
> > difficult to make a service activatable both via dbus and via some other
> > mechanism properly, in a fully parellelized environment: because
> > activation via dbus might cause a different env to be passed to a
> > service than activation via socket, hw plugin, manual user or at boot or
> > any other.
> The flip side of course is that not starting these services with the
> D-Bus activation environment if activated from D-Bus would mean that
> the service would get different environment whether or not Upstart or
> systemd were actually in use!
Well, but that less ugly I would say. Also, most people I think agree on
that bus-wide runtime-changable env blocks that are passed to services
are ugly anyway. While we might not outright deprecate this right-yet we
might want to do this eventually.
They way I see this is that the env block stuff is a hint for the
classic activator code, but not more.
Lennart Poettering - Red Hat, Inc.
More information about the dbus