http://defect.opensolaris.org/bz/show_bug.cgi?id=13166
Darren Kenny <dkenny at opensolaris.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dkenny at opensolaris.org
--- Comment #8 from Darren Kenny <dkenny at opensolaris.org> 2009-12-10
08:04:31 UTC ---
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> In the cases where nwamadm is running with the appropriate environment then it
> should set it up. When there isn't the appropriate environment then there is
> nothing we can do anyways to make zenity or whatever run. I don't see why we
> should treat clients differently.
I think that I would agree with Michael here, why make it different - if the
information is there, it's there, otherwise it's not.
> >
> > Yeah, it seems a bit hacky to take the pieces from the GUI user environment
> > and
> > add them to the netadm user's environment in order to get the display
> > working
> > for ENMs. On the other side, we can't just run as the GUI user since that
> > leaves us without options when the GUI is not present (it would be weird if
> > we
> > ran ENM scripts as netadm when the GUI wasn't present but as the GUI user
> > when
> > it was). Not sure what the right answer is here...
>
> I not saying run as the GUI user. I'm saying run as the control program user
> (e.g. nwamadm). The sticky point is when we are automatic and nobody has
> talked to us. The cases I can think of:
>
> * enterprise - text only
> * startup - gnome isn't available yet
> * triggered invocation of ENM
>
> In all of these cases there is no guarantee of interaction. If the user
> doesn't have a GUI and wants to use an ENM that needs interaction then I think
> it is okay to leave him on his own. We could have a registry program which
> the
> user could invoke which merely tells us what the environment to run ENMs as
> (or
> as an option to nwamadm). Then in GUIless environments where the user wants
> interaction then we could pass him a reasonable environment (one with fds
> pointed at /dev/console being the major point?).
I think that an ENM will need to have a property added to say something like
"requires desktop environment" - so that nwamd can simply fail it if there is
no appropriate client (with the env set).
If you try to run the GUI as the control program user, you may run into other
issues like:
- Connection to GConf database, you can't connect to the same user's
configuration database, which could easily result in you using the wrong
theme/fonts, etc - which can look really bad...
- Connection to the user's Dbus session to sent notification, or similar, will
fail since you are not the same UID.
- Reading from the user's XAUTHORITY file will most likely not work if not
done as the user since the mode on the file tends to be 0600...
and so on. So I think that you *must* run the GUI type app as that user...
--
Configure bugmail: http://defect.opensolaris.org/bz/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
