Paul Melis wrote: > I'm suspicious of the line "vglclient is already running [...]" when > running vglconnect, as I don't see any vglclient running on the client: > > pa...@sara0143:~$ ps aux|grep vgl > paulm 11262 0.0 0.0 1772 524 pts/2 S+ 11:27 0:00 /bin/sh > ./vglconnect -s loom > paulm 11273 0.0 0.1 6140 2532 pts/2 S+ 11:27 0:00 ssh -t > -Y -R59809:localhost:4242 loom /opt/VirtualGL/bin/vgllogin -s 59809 > paulm 11447 0.0 0.0 3004 768 pts/1 S+ 11:31 0:00 grep vgl > > > So, there should be a vglclient running on my client machine? This used > to work a few weeks ago, but I'm in the dark as to what changes on my > systems cause it to fail now. > Well, running vglclient -force seems to have reset things. vglconnect now correctly spawns a vglclient again. How exactly does vglclient check if it's running?
Paul ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ VirtualGL-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/virtualgl-users
