Here's what I observe. Let's take three machines, {VGLCLIENT},
{SSHCLIENT}, and {SERVER}. I modified vglrun such that it prints the
value of VGL_CLIENT before executing the 3D program.
{VGLCLIENT}:
-- Enable X11 TCP connections
-- Log in to X server
-- xhost +{SERVER}
-- Start vglclient
{SSHCLIENT}> ssh -x {SERVER}
{SERVER}> vglrun /opt/VirtualGL/bin/glxspheres
[VGL] NOTICE: Automatically setting the DISPLAY environment variable to
[VGL] {SSHCLIENT's IP}:0.0, based on the IP address of your SSh client.
VGL_CLIENT=
Polygons in scene: 62464
ERROR (549): Could not open display
Expected, because there is no X server running on {SSHCLIENT} at the
moment. Now,
SERVER> vglrun -cl {VGLCLIENT} /opt/VirtualGL/bin/glxspheres
[VGL] NOTICE: Automatically setting the DISPLAY environment variable to
[VGL] {SSHCLIENT's IP}:0.0, based on the IP address of your SSh client.
VGL_CLIENT={VGLCLIENT}
Polygons in scene: 62464
ERROR (549): Could not open display
Same as above. VGL_CLIENT is being set correctly, but DISPLAY needs to
also be set.
SERVER> export DISPLAY={VGLCLIENT}:0.0
SERVER> vglrun /opt/VirtualGL/bin/glxspheres
VGL_CLIENT=
This succeeds, because if VGL_CLIENT is not set, VirtualGL will first
look at the value of DISPLAY and try to find a running instance of
vglclient on that machine.
SERVER> export DISPLAY={VGLCLIENT}:0.0
SERVER> vglrun -cl {VGLCLIENT} /opt/VirtualGL/bin/glxspheres
VGL_CLIENT={VGLCLIENT}
This succeeds as well, because the value of VGL_CLIENT explicitly tells
VirtualGL where to look for the running instance of vglclient.
Everything is working exactly as expected.
On 12/15/10 4:26 PM, Philippe wrote:
> I checked the value of VGL_CLIENT and nothing what set, then I set
> VGL_CLIENT=CLIENT1 and keep -cl CLIENT1 in the vglrun command line, and
> I still get the same result, the only way to resolv the issue was to set
> DISPLAY=CLIENT1:0.0 :)
>
> On Wed, Dec 15, 2010 at 9:50 PM, DRC <[email protected]
> <mailto:[email protected]>> wrote:
>
> The normal behavior is for vglrun to parse the value of the
> SSHCLIENT environment variable, which should contain the IP address
> of ME in your case, and set VGL_CLIENT from this. However,
> specifying vglrun -cl will override this behavior. I think you may
> be misdiagnosing the issue. I suspect that VGL_CLIENT is being set
> properly when you specify vglrun -cl, but since vglclient and your X
> server are running on a different machine from your ssh client
> machine, you have to explicitly set both DISPLAY and VGL_CLIENT to
> point to that machine in order for VGL to work properly.
>
>
> On Dec 15, 2010, at 1:41 PM, Philippe <[email protected]
> <mailto:[email protected]>> wrote:
>
>> I specified the CLIENT1 IP (consider I'm NOT the CLIENT1, I'm me
>> :) ), then here is what I try to do :
>> ME > ssh > SERV1 > vglrun -cl CLIENT1 > CLIENT1 (vglclient listening)
>> In this configuration, like you said, vglrun take care of MY IP
>> instead of CLIENT1 IP, and then try to connect to MY vglclient
>> (who's not running) instead of CLIENT1 vglclient.
>> Is it normal ?
>> So the solution, for the moment, is to set $DISPLAY=CLIENT1:0.0 .
>>
>> On Wed, Dec 15, 2010 at 7:51 PM, DRC
>>
>> <<mailto:[email protected]>[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> The option is still supported, and it's documented in the
>> User's Guide
>> (under Advanced Configuration), but it isn't listed in the
>> vglrun output
>> because it isn't a commonly-used option.
>>
>> vglconnect eliminated the need to run vglclient manually as you're
>> describing, so most people use vglconnect. Also, vglrun will
>> automatically set VGL_CLIENT to the IP address of your client
>> machine if
>> you are using SSh, so even if you aren't using vglconnect, it
>> still
>> should not normally be necessary to set VGL_CLIENT manually.
>>
>> The -cl option works as I expect, and its behavior has not changed
>> significantly in years. Not sure why it isn't working for you.
>>
>> On 12/15/10 8:25 AM, Philippe wrote:
>> > Hello,
>> > I got a problem recently, first, in vglrun --help there's no more
>> > indications about the -cl option, but it's always in the online
>> > documentation, is it normal ?
>> > And second, (I don't use vglconnect, I just connect myself
>> from my
>> > computer with ssh and launch vglrun from SERV1 to CLIENT1
>> with vglrun
>> > -cl CLIENT1 and vglclient listening on CLIENT1) SERV1 doesn't
>> take care
>> > of the -cl argument, it uses my IP instead of the CLIENT1 IP.
>> >
>> > I don't understand why.
>> >
>> > Is the -cl argument always available ?
>> >
>> > Thanks for help.
>> >
>> > Philippe.
>> >
>> >
>> >
>> >
>> ------------------------------------------------------------------------------
>> > Lotusphere 2011
>> > Register now for Lotusphere 2011 and learn how
>> > to connect the dots, take your collaborative environment
>> > to the next level, and enter the era of Social Business.
>> >
>> <http://p.sf.net/sfu/lotusphere-d2d>http://p.sf.net/sfu/lotusphere-d2d
>> >
>> >
>> >
>> > _______________________________________________
>> > VirtualGL-Users mailing list
>> >
>> <mailto:[email protected]>[email protected]
>> <mailto:[email protected]>
>> >
>> <https://lists.sourceforge.net/lists/listinfo/virtualgl-users>https://lists.sourceforge.net/lists/listinfo/virtualgl-users
>>
>>
>> ------------------------------------------------------------------------------
>> Lotusphere 2011
>> Register now for Lotusphere 2011 and learn how
>> to connect the dots, take your collaborative environment
>> to the next level, and enter the era of Social Business.
>>
>> <http://p.sf.net/sfu/lotusphere-d2d>http://p.sf.net/sfu/lotusphere-d2d
>> _______________________________________________
>> VirtualGL-Users mailing list
>>
>> <mailto:[email protected]>[email protected]
>> <mailto:[email protected]>
>>
>> <https://lists.sourceforge.net/lists/listinfo/virtualgl-users>https://lists.sourceforge.net/lists/listinfo/virtualgl-users
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Lotusphere 2011
>> Register now for Lotusphere 2011 and learn how
>> to connect the dots, take your collaborative environment
>> to the next level, and enter the era of Social Business.
>> http://p.sf.net/sfu/lotusphere-d2d
>> _______________________________________________
>> VirtualGL-Users mailing list
>> [email protected]
>> <mailto:[email protected]>
>> https://lists.sourceforge.net/lists/listinfo/virtualgl-users
>
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
> _______________________________________________
> VirtualGL-Users mailing list
> [email protected]
> <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/virtualgl-users
>
>
>
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
>
>
>
> _______________________________________________
> VirtualGL-Users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/virtualgl-users
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
VirtualGL-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/virtualgl-users
