[PATCH 0/5] Support service activation through Upstart
Scott James Remnant
scott at netsplit.com
Sat Dec 25 12:18:30 PST 2010
On Sat, Dec 25, 2010 at 3:59 PM, Lennart Poettering <mzqohf at 0pointer.de> wrote:
> On Sat, 25.12.10 15:29, Scott James Remnant (scott at netsplit.com) wrote:
>> > Hmm, I am quite opposed to this. I think we are well advised not to
>> > extend D-Bus .service files functionality-wise, to ensure that
>> > regardless which method of activation you use the same behaviour takes
>> > place. Or with other words: it's fine to shift around the place where
>> > activation is executed (the ActivationString= can be used for that), but
>> > it's a bad idea to make it behave completely differently (which I fear
>> > the service stuff could trigger).
>> How does this extend the D-Bus .services files in any way?
> Because your env stuff is passed along only if the service is activated
> by Upstart, but not otherwise. Hence the stuff encoded in the .service
> file is handled differently in its effect on Upstart and on the classic
Ah, I see the misunderstanding.
The "env" stuff in the signal is the D-Bus activation environment
only, that D-Bus would use if it was to activate the job itself, and
that can be updated by UpdateActivationEnvironment for session
There's no Upstart-specific stuff in there, perhaps I confused you by
prepending the service name etc. in my current method call - in the
signal I proposed, those are separate arguments to closer match yours.
More information about the dbus