On Nov 24, 2011, at 2:16 PM, Arthur Huillet <arthur.huil...@free.fr> wrote:
> On Thu, 24 Nov 2011 14:06:23 -0600 > DRC <dcomman...@users.sourceforge.net> wrote: > >> You're misunderstanding. vglgenkey does work on RHEL 6 if you disable >> SELinux. However, it doesn't work by using the X Security extension. It >> simply makes a copy of the existing gdm xauth key, but it needs access >> to /usr/bin/xauth to do that, and SElinux disallows that from within the GDM >> context. > > Alright, so it relies on gdm, and my installation doesn't use it so that's why > it wasn't working. > At any rate, wouldn't it be good to figure out how gdm does its xauth key > generation and reproduce this? > > I think I am being confused. It should also work with xdm or kdm. If it doesn't, then that's a bug. gdm is generating the key internally using the same mechanisms that xauth uses. The basic point is that VirtualGL needs access to the display while the DM is running. It can do that by generating a new xauth key for the display, but that requires the X Security extension. It can also copy the existing key that the DM has already generated for itself. Maybe we should approach this from a different angle. Is something not working properly, or is there functionality you need that doesn't exist? ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
