Wild guess: dxui uses a port ("-appPort 1920") to connect to the
executable. This is probably changeable using some command line option.
Could it be that that port is taken up? Maybe your ssh is set up to
forward this port and only for one machine, not for the other.Richard Cook wrote: > > Hello, when I attempt to ssh to our IBM AIX machine from my office > (an SGI indigo2 box with IRIX 6.5) and run dx, I can run the dxui > front end, but if I then try to run, say the editor from there, it > complains that it cannot connect to dxexec. > However, if I ssh to the same account on the same machine, but this > time ssh FROM a different SGI (an Onyx running IRIX 6.5 in another > building, possibly another network subnet), I can run dx and then > spawn the dx editor as you would expect, with no troubles. > > WHY OH WHY do I get this error from one box and not from the other? > This is not a problem with paths, libraries, or other configuration > issues on the AIX machine, because I ssh to the same account on the > same machine. The ONLY difference between the two situations is the > machine from which I ssh. > > I believe the problem is perhaps related to dxui, a program which is > launched by the DX front end when you click on one of its buttons. I > notice (by observing that the front end "edit visual programs" button > launches the following command: > > /usr/local/OpenDX/4.1/dx/bin_ibm6000/dxui -edit -memory 128 -processors > 1 -xrm DX.editorWindow.geometry:-0+0 -appPort 1920 -wizard -directory > /usr/local/OpenDX/4.1/dx/bin > > When I try this command from the command line, it fails to work as > well, UNLESS I eliminate the -appPort 1920 line, in which case it > fires up the editor and server correctly!!!! > > I am really confused, help! Thanks. > --
