VirtualGL is an interposer, so it is loaded into individual processes. It cannot be launched at startup, nor would it be meaningful to do so. If you are using TurboVNC, then it is possible to:
1. Launch a specific TurboVNC session for a specific user at startup. If your chroot environment supports init.d (or init.d emulated with systemd, which most modern Linux distros support), then after installing TurboVNC, you should be able to enable the tvncserver service (using 'sudo systemctl enable tvncserver', for instance) and edit /etc/sysconfig/tvncservers in order to launch a TurboVNC session at startup. 2. Use VirtualGL to launch the window manager in that TurboVNC session, so VirtualGL is automatically loaded into any OpenGL applications that are launched within that session. You can do this by adding '-vgl' to the VNCSERVERARGS variable in /etc/sysconfig/tvncservers. Apart from that, if there are problems you encounter that would apply to any configuration of VGL and TurboVNC, then I'm happy to address those, but in general, running VGL in a chroot environment isn't supported. On 5/19/19 7:49 AM, Ivi wrote: > I made it to install vgl with gl4es. > What should I do to launch vgl at startup? > -- You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to virtualgl-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/d14f0e5f-6e57-a81a-d987-fa2d885d3561%40virtualgl.org. For more options, visit https://groups.google.com/d/optout.
