If you use vglconnect, then it automatically starts vglclient and redirects the output to a log file in ~/.vgl, which is where the profiling output will be. You can do tail -f <logfile> to see this in real time.
On Feb 10, 2010, at 4:01 AM, Paul Melis <[email protected]> wrote: > Hello, > > When doing VGL Image Transport it's easy to get profiling data on the > server side (vglrun +pr), and the docs mention the env.var. > VGL_PROFILE > to enable it on the client side as well. But how is that supposed to > work? Should I do this? > > [client] export VGL_PROFILE=1 > [client] vglconnect -s <host> > [server] vglrun ... > > If so, where does the client-side profiling data go? If this isn't the > way to do it, how should one use the VGL_PROFILE setting? > > Thanks, > Paul > > --- > --- > --- > --------------------------------------------------------------------- > SOLARIS 10 is the OS for Data Centers - provides features such as > DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > VirtualGL-Users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/virtualgl-users ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ VirtualGL-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/virtualgl-users
