We most definitely should not clear the environment. That will break a lot of things. For instance, passing environment variables into the VNC session is necessary when using VirtualGL and VNC in a batch queuing environment. With current solutions (based on TurboVNC), the scheduler will choose a GPU that is the least busy and will launch vncserver with VGL_DISPLAY set to the appropriate value for that GPU. Thus, any 3D applications the user decides to launch will run on the assigned GPU.
Adam Tkac wrote: > On Wed, May 20, 2009 at 10:32:37AM +0200, Pierre Ossman wrote: >> On Wed, 20 May 2009 10:10:57 +0200 >> Adam Tkac <at...@redhat.com> wrote: >> >>> Proposed patch (1.0 + trunk) is attached. >>> >> Looks good to me. >> >> Perhaps we should go one step further and start with a clean >> environment? > > I'm not sure if this is the right approach. > > If you unset all environment variables then it might be quite hard to > set "standard" set of variables (for example /etc/profile* variables > will be set only via login, AFAIK) > > Next problem is that you will start multiple instances of services > which don't have to be run per session (like ConsoleKit, ssh-agent etc). > > Regards, Adam > ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
