http://defect.opensolaris.org/bz/show_bug.cgi?id=13166
--- Comment #3 from amaguire <alan.maguire at sun.com> 2009-12-09 17:28:38 UTC --- (In reply to comment #2) > (In reply to comment #1) > > So we need to lookup a console login user as we did before to get the value > > for > > HOME and also set DISPLAY explicitly in the environment I think. > > I was wondering if the caller's environment information or some useful bit of > information might be available from the door; that would give us a more > obvious > choice in the case where the enm was manually enabled/disabled. > > That wouldn't work in the case of conditionally activated enms, of course. > But > I'm nervous about adding the user lookup stuff back in--that has been pretty > fragile in phase 0/0.5. The format of the data and the identification of the > console user seems to vary depending on how you login, so we had problems > working with gdm, for example. And I suspect virtual consoles change things, > too. We definitely need to tread carefully here. > > The GUI is running under the console user's environment, right? Any chance we > could exploit that? I wonder if we need to take a step back here and figure out what the execution environment of the ENM scripts should be. At present, they run as user/group netadm/netadm. Is there a way that we can ensure this user has access to the display rather than grabbing settings from other user's environments, e.g. by setting up an .Xauthority file in netadm's HOME directory? I tried experimenting with xauth but without success. Maybe Darren might have some suggestions here... -- 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.
