Re: [ProgSoc] xhosts and xservers etc

[Rob Lowe <robert@nospam.access.com.au>]

On Thu, 4 Mar 1999, James Wan wrote:

] Yeh on the server, you have to do a setenv, which allows your x-client
] access to the display.

More specifically, set the DISPLAY environment variable (using setenv, if using
csh) should be set to:

DISPLAY=clientIP:0.0

] and on your xclient, you use the xhost command to that x-server.

xhost is required if an X server is running on the client machine. If it's the
'Xwin thingy' you should just need to point it at ftoomsh (not sure off hand
how to do this - prompted when opening the X session ?).

] 
] 
] On Thu, 4 Mar 1999, Vik wrote:
] 
] > Greetings all,
] > 
] > I am under the impression one can run X-apps on ftoomsh with the display
] > and input going to/coming from a local machine (I am not using the words
] > server and client as I can never remember which is which  :) If this is
] > so, does one need to configure any files on the remote machine (ftoomsh)?
] > And what would one need to do on the local machine (likely  to be a
] > win3.11 box with a Xwin thingie). Any tricks/tips/ideas/abuse?

--
  Robert Lowe                                 robert@nospam.access.com.au    
  Access Systems Research Pty. Ltd.           Tel: +61 2 9957 1036    
  * ACES * Internet Gaming Software       http://www.access.com.au

--
You are subscribed to the progsoc mailing list. To unsubscribe, send a
message containing "unsubscribe" to progsoc-request@nospam.progsoc.uts.edu.au.
If you are having trouble, ask owner-progsoc@nospam.progsoc.uts.edu.au for help.

This list is archived at <http://www.progsoc.uts.edu.au/lists/progsoc/>