On Fri, Jan 02, 2004 at 03:33:42PM +0100, Alexander Gottwald wrote:
> On Fri, 2 Jan 2004, Chris Green wrote:
>
> > The trouble is that when I run 'xhost 127.0.0.1' in a cygwin window on
> > my win2k system I just get the error:-
> > xhost: unable to open display ""
>
> that would be DISPLAY=127.0.0.1:0 xhost 127.0.0.1
>
> But most likely you will have no access from windows. Run xhost from the
> session started via xdmcp.
>
But if I run xhost in that session I will be setting xhost permissions
on the Linux Slackware system which is most definitely not what is
required.
It seems very odd that xhost requires access to the local display in
order to work as you need xhost to set permission to acces the local
display - sort of catch 22.
If I open just a cygwin terminal window on my Win2k system I simply
can't run xhost at all.
E.G.:-
$ xhost
xhost: Unable to open display ""
$ export DISPLAY=192.168.13.25:0.0
$ xhost
Xlib: connection to 192.168.13.25:0.0 refused by server
Xlib: no protocol specified
xhost: Unable to open display 192.168.13.25:0.0
So how can one ever run xhost (and thus xwinclip)?
> > What should the DISPLAY environment variable be set to for the local
> > display? I'm used to setting it for remote systems but I can't get
> > the right value for this one.
>
> Fot the local display this is 127.0.0.1:0 or :0
>
Maybe my win2k set up is wonly but 127.0.0.1 won't work for me, the
actual IP address of 192.168.13.25 does work though. However a second
try seems to be OK, maybe I'd got into a mess before. The 'catch 22'
above still applies though.
--
Chris Green ([EMAIL PROTECTED])
