19990914: xhost. (cont.)

>From: Jim Heimbach <address@hidden>
>Organization: UNCA
>Keywords: 199909141652.KAA04088 McIDAS

Jim,

>     Maybe what I am trying to do is not possible.  I would have thought
>that my plans wouldn't require the use of xhost, etc. 
>     O.K., I have the mcidas account established on vortex and this
>account is not to be used by folks.

Sounds good.

>There is a user account called 
>uncamcid which the rest of the world is to use.

OK just as long as each concurrent user running in the 'uncamcid' account
has his/her own McIDAS working directory.  I discussed the need for this
in earlier emails.

>I can run mcidas under
>uncamcid on vortex (the ULTRA-2 server)

OK, good.

>My goal was to run mcidas
>on the uncamcid account on tornado by accessing the
>programs in /vortex/home/mcidas/bin and the like which
>are nfs'd.

This sounds like it should work to me.

>I was not planning to have vortex do the running, then 
>display on tornado,

I understood that.

>I want tornado to do the work and its own display.

I understand.

>uncamcid is the user which is logged on and started X on tornado.

OK.  This should mean that 'uncamcid' should be able to start X stuff.
Since starting McIDAS failed, perhaps you should start simply and
see if you can start an xterm in the same environment (i.e. login,
start X, have .cshrc define DISPLAY, and see if running 'xterm'
will start an X terminal).

>I used 
>the which command to verify that uncamcid logged onto tornado can
>access all the files nfs'd on vortex.

OK good.  What does something like:

ldd `which df.k` return?

If there are shared libraries listed that could not be found, then
the Ultra environment is different from the SPARCstation 5.

>     Both machines are running SOLARIS 5.7.  Could a program compiled
>on an ULTRA-2 not run on a SPARCstation-5?

I believe that they should be runnable on both.  Try the ldd command
above to see if this is true.

>     Does that make any sense or am I opening a can of worms?

I do not think that you are opening a can of worms.  This is the sort
of thing that I would try.

Tom

>From address@hidden  Wed Sep 15 09:59:55 1999

     You were correct on start-X being the problem.  Although
I went to lengths to get the DISPLAY set up as a function of
machine, I goofed and kept an old set DISPLAY later in .cshrc.
     The next error was the shared memory segment thing.  I had
forgotten to set that up for tornado.
     Now it runs as advertised!  Many thanks for the help.  Now
I will get to work getting XCD up.
                  -- Jim H