This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
xwinclip not waiting for x server startup (was xwinclip authorisation)
- From: "Matthew Donald" <matthew dot donald at motile dot net>
- To: <cygwin-xfree at cygwin dot com>
- Date: Tue, 15 Jan 2002 23:12:06 +1100
- Subject: xwinclip not waiting for x server startup (was xwinclip authorisation)
Hi Shane,
Cygwin/Xfree and XDMCP work correctly. I only get a problem when running a
local X client at the same time as a remote X client (via XDMCP). It turns
out a /etc/X0.hosts file containing a 'localhost' entry is needed. Also
xwinclip does not wait for the X server to complete startup, while some
other clients (such as xterm) do.
Any ideas why xwinclip does wait for X server startup?
cheers Matthew
----- Original Message -----
From: "Shane Shields" <locutusenterprises@yahoo.com>
To: "Matthew Donald" <matthew.donald@motile.net>
Sent: Tuesday, January 15, 2002 4:55 PM
Subject: Re: xwinclip authorisation problem with remote hosts using XDMCP
>
> --- Matthew Donald <matthew.donald@motile.net> wrote:
> > Hi,
> >
> > There is a problem when using xwinclip with an X
> > server which connects to a
> > remote host using XDMCP.
> >
> > Basically the sequence is this:
> >
> > 1. Execute "XWin :0 -query some.host.system".
> > Initially, the authorisation
> > file contains no records, so the localhost
> > has access to the X server by default. I quote from
> > the Xserver man page:
> >
> > If this file contains any authorization
> > records, the
> > local host is not automatically allowed
> > access to the server, and
> > only clients
> > which send one of the authorization records
> > contained in the file in the
> > connection
> > setup information will be allowed access.
> >
> > 2. XDMCP is used to query some.host.system, which
> > then opens a connection
> > to the local PC. The first
> > thing done is that XDMCP adds an auth record for
> > some.host.system This
> > means that localhost loses access
> > to the X server.
> >
> > 3. After XWin starts, xwinclip executes on the
> > local host. It fails with
> > the error message: "Could not open display"
> >
> > Ok, so I added an xhost command, to explicitly allow
> > access:
> >
> > xhost +127.0.0.1
> >
> > I failed with the error messages:
> >
> > Xlib: connection to "127.0.0.1:0.0" refused by
> > server
> > Xlib: Client is not authorized to connect to
> > Server
> >
> > I read some more about host access, and I created a
> > /etc/X0.hosts file, and
> > I deleted the .Xauthority file.
> > This caused a different error. XWin failed with the
> > message: "X connection
> > to 127.0.0.1:3.0 broken
> > (explicit kill or server shutdown)."
> >
> > I tried running XWin with the '-ac' command line
> > parameter. This is meant
> > to open access to all hosts.
> > Xwinclip still couldn't open the display.
> >
> > If XWin is used with a local window manager, this
> > xwinclip (and any other
> > client program which runs on the PC)
> > will run sucessfully. However, if XDMCP is used to
> > connect to another
> > system, then it fails.
> >
> > I'm completely stuck. Any help would be very
> > appreciated.
> >
> > regards Matthew
> >
> >
> >
>
> have you opened up the xdmcp port in hosts.allow
> otherwise it wont let you in
>
>
> __________________________________________________
> Do You Yahoo!?
> Send FREE video emails in Yahoo! Mail!
> http://promo.yahoo.com/videomail/
>