> One more random question on the issue - when I try to connect to the
> Zoo via XDMCP query (command line 'xinit -- -query
> rhino.cs.yale.edu'), I repeatedly get the message
>
> AUDIT: Mon Apr 5 20:28:32 1999: 12761 Xwrapper: client 9 rejected from
> local host
> Xlib: connection to ":0.0" refused by server
> Xlib: Client is not authorized to connect to Server
> ..
That's an interesting problem. What's happening is that the new X server
you're running isn't allowing a client from your own system to access it.
This is perfectly normal: you want clients from the current session, not
outside programs, to be able to access an X server.
The problem arises in the first place because you're using xinit (or
startx, which calls xinit) which does two things: starts an X server and
sends an initial client to it. (By default, it sends an xterm window, but
that doesn't really matter.) It's this client that's unable to connect
and which, therefore, repeatedly causes the error you're seeing.
You can fix it by running Xwrapper directly. It doesn't attempt to start
any client programs; it just sets up the X server. For example, just run
'Xwrapper -query rhino.cs'.
A more general solution is to fix access control on your new server. If
you're the only person who uses your machine, this can be as simple as
'xhost +your.machine.yale.edu' from a shell run inside the new display
(or anything else that has access to connect, assuming you set DISPLAY
appropriately before running 'xhost').
Shawn