rjvo |
01/03/2014 06:27PM (Read 4989 times)
|
|
|
Status: offline
Registered: 04/21/2007
Posts: 134
|
I did
PHP Formatted Code ssh -X oldhost
and I was able to get "xterm" but not "xgterm" which complains:
PHP Formatted Code _X11TransSocketINETConnect : Can 't get address for localhost
Why is so?
|
|
|
|
fitz |
01/03/2014 07:02PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
Make sure you have a 'localhost' definition in the /etc/hosts file that looks something like
127.0.0.1 localhost
This is used to redirect traffic from the server to the client during X11 forwarding.
|
|
|
|
rjvo |
01/03/2014 07:07PM
|
|
|
Status: offline
Registered: 04/21/2007
Posts: 134
|
Sure, there is localhost in hosts. The "xterm" and other X-apps run without any problem. There is a ploblem with the xgterm.
|
|
|
|
fitz |
01/03/2014 07:10PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
What are the two platforms involved (e.g. ssh from Mac to linux, linux-to-linux, etc)?
|
|
|
|
rjvo |
01/03/2014 07:20PM
|
|
|
Status: offline
Registered: 04/21/2007
Posts: 134
|
linux - linux
|
|
|
|
fitz |
01/03/2014 07:32PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
Does using "ssh -X -Y oldhost" make a difference? What is the value of $DISPLAY after you log in?
|
|
|
|
rjvo |
01/03/2014 08:21PM
|
|
|
Status: offline
Registered: 04/21/2007
Posts: 134
|
PHP Formatted Code
$ ssh -X -Y oldhost
$ xgterm
_X11TransSocketINETConnect : Can 't get address for localhost
xgterm Xt error: Can't open display : localhost :11.0
$ echo $DISPLAY
localhost :11.0
|
|
|
|
fitz |
01/03/2014 09:14PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
Try setting your DISPLAY value directly instead of using a forwarding address, e.g.
newhost\$this->_split2($m[0]) xhost +
newhost\$this->_split2($m[0]) ssh -XY oldhost
oldhost\$this->_split2($m[0]) setenv DISPLAY newhost:0.0
oldhost\$this->_split2($m[0]) xgterm
The difference between XTerm and XGterm might just be that an XTerm resource defines a loginShell resource but XGterm doesn't and your .login file does/doesn't define $DISPLAY explicitly.
Additionally, if you ssh'd into the first machine and then to the second, be sure the '-X' flag is used with each login.
|
|
|
|
rjvo |
01/04/2014 08:49AM
|
|
|
Status: offline
Registered: 04/21/2007
Posts: 134
|
This solution does NOT work.
I did something what worked before. I dowloaded
x11iraf-v2.0BETA-bin.linux.tar.gz 2.5 MB 9/2/09 2:00:00 AM
from
ftp://iraf.noao.edu/iraf/x11iraf/
and extracted the xgterm which works fine without any work-around. It simply works like xterm.
THEREFORE: we have a problem with XGTERM in the new IRAF distro.
|
|
|
|
fitz |
01/16/2014 08:59PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
To close out the thread:
The statically linked binaries are included in the v2.16.1 distribution as the default because increasingly 64-bit linux distributions no longer come with 32-bit compatibility libraries by default, and the instructions for how to install needed 32-bit libs vary widely depending on the platform in question. These binaries were built using an older version of GCC since newer versions won't allow static linking due to system procedures such as gethostbyname() requiring a dynamic glibc (and thus the 32-bit compatibility libs as well). I think the reason the static binaries don't work, but the dynamic binaries you got from the x11iraf-v2.0BETA-bin.linux.tar.gz file do, is because the static binaries violate the requirement for a dynamic glibc for things like name resolution (i.e. this is why 'localhost' isn't resolved).
In future releases I'll provide both the static AND dynamic binaries in the distribution as well as notes about how and when to use which version. This will basically leave the choice of either installing 32-bit libs, or living without the ability to remotely display the window. There are no plans to make 64-bit versions of the X11IRAF tools available due to the large number of legacy widgets in the GUI toolkit, a much more do-able project is to support a 64-bit XGterm that only does graphics (no GUIs and no XImtool), however that is not currently on the roadmap either.
|
|
|
|