X Server Can't Connect and Forcing use of FQDN

LinuxGeek · 04-09-2006, 01:07 PM

Hi,
I have a commercial application that is trying to access an X server that is composed of the machine's FQDN and 0.0. Unfortunately, it seems that there is no way to override this via the application. Is there any workaround so that I can make it use the native :0.0 instead? Thanks for your help.

coolb · 04-09-2006, 01:14 PM

Quote:

Originally Posted by LinuxGeek

Hi,
I have a commercial application that is trying to access an X server that is composed of the machine's FQDN and 0.0. Unfortunately, it seems that there is no way to override this via the application. Is there any workaround so that I can make it use the native :0.0 instead? Thanks for your help.

umm.. If I understand you right, your commercial app is trying to connect to your machines X windows server using it's FQDM and your X server isent listening on the FQDM, and you want the app to connect to localhost:0... I have an idea, why not edit /etc/hosts and make the FQDM(the one that the app is using) 127.0.0.1 and the it can connect to localhost(where your X server is) and magic :-)

LinuxGeek · 04-09-2006, 02:31 PM

Thanks for you input coolb. I tried it out quickly but unfortunately it didn't work

What's I'm trying to do is get it to use :0.0 (not localhost:0.0 or FQDN:0.0). Do you think something like creating a socket under /tmp with the FQDN and soft linking it to the :0.0 socket would do the trick?

LinuxGeek · 04-10-2006, 11:35 AM

I did a workaround using gdm.conf and adding the necessary cookie. Another approach is to run a vnc server and make it attach to the X server that the application is looking for.

LinuxGeek · 04-10-2006, 12:22 PM

I did a workaround using gdm.conf and adding the necessary cookie. Another approach is to run a vnc server and make it attach to the X server that the application is looking for.