🚀 go-pugleaf

In article <TALE.89Mar25022854@ts.its.rpi.edu> tale@pawl.rpi.edu writes:
>
>A more specific example:
>I login to consult1.its.rpi.edu and fire up my X11R3 server with
>vanilla uwm.  I turn around and login to risk.its.rpi.edu, an
>identical (for all practical purposes) machine.  From risk, I start
>"emacs -display consult1.its.rpi.edu:0" and it complains about not
>being able to connect to the X server; in fact, if I try using that
>display from consult1, it still balks, although -display unix:0 works
>as it should.  The problem does not seem to be with our network or
>with X, as other X tools (xterm, xclock, xcalc, et al) work as
>expected.

In order for one machine to behave as a client to a server running on
another machine, the server machine must have the client machine
listed in its `hosts that are permitted to use me' list (accessed
through the `xhost' command).  In your case, it seems running:

consult1.its.rpi.edu% xhost risk.its.rpi.edu consult1.its.rpi.edu

will work.  I know 18.53 and 18.52 work with X both locally and
remotely since I am using it now.  If this does not solve your problem
you may give me a call or send me mail.

Christopher Welty  ---  Asst. Director, RPI CS Labs | "Porsche:  Fahren in
weltyc@cs.rpi.edu             ...!njin!nyser!weltyc |  seiner schoensten Form"