On Sun, 2007-10-28 at 17:02 -0400, Dan Williams wrote:
On Sun, 2007-10-28 at 07:53 -0400, Jesse Keating wrote:
> On Sun, 28 Oct 2007 10:10:28 +0100
> Alexander Boström <abo(a)kth.se> wrote:
>
> > sön 2007-10-28 klockan 01:10 -0400 skrev Dan Williams:
> > > This sounds pretty wrong; root isn't supposed to know about the
> > > session
> > > bus, and you're going to have a very hard time finding out the
> > > address of some random user session bus by design.
> >
> > Yup. And a user might have multiple sessions on a single computer.
> > Think multiple logins to the guest account, or one log in through GDM
> > and one session established via ssh. Stuff like that happens.
>
> If this is the case, then wouldn't it make sense to have a
> NetworkManagerDispatcher option to run things in the active session?
Except for the fact that as root, NMD can't find out the session bus
address, nor should it be able to.
Plus lots of other things as it would have to change user / selinux
context etc. etc. I think maybe you want nm-applet (or a NMD with a
--session option) to just run stuff from
/etc/NetworkManager/session-dispatcher.d/
as the user of the session. Then the natural progression is that you
also want
~/.NetworkManager/session-dispatcher.d
so an unprivileged user can drop stuff in his own home directory that
gets run on events. Thoughts?
David