set user id for service ?

David Zeuthen david at
Tue Sep 19 12:43:52 PDT 2006

On Sat, 2006-09-16 at 01:48 +0100, Scott James Remnant wrote:
> So one assumption to correct is that upstart wouldn't listen to events
> from HAL, we'd have something that decided when it was appropriate for a
> job upstart might manage to be started, and tell upstart.

Well, HAL spits out lots of events, sure only some are useful. That's
because HAL doesn't try to enforce any policy; it leaves that to e.g.

> GNOME Power Manager is an example of something that does one thing,
> dealing with power management, and does it well.

One question: how can you trust the events that g-p-m would send to
upstart are genuine? Ie. how do you ensure that they don't come from a
malicous attacker? Seems like you can't do this securely...

> The one thing that it cannot do, at least with the current design (and
> I've no plans, unless someone wants it), is:
>  * start a service or task inside an existing user's existing session
> I'd argue that's the job of the session manager; or volume manager,
> which appears to be doing a lot of this kind of thing.

Right. That's, for example, why I filed

for g-p-m to run user scripts when significant events happen.


More information about the dbus mailing list