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.
: "Brian Genisio" <[EMAIL PROTECTED]>
To: "Matthew Donald" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, January 15, 2002 6:25 AM
Subject: Re: xwinclip authorisation problem with remote hosts using XDMCP
> What is your DISPLAY variable set to? I a
- Original Message -
From: "Alexander Gottwald" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, January 15, 2002 7:08 PM
Subject: Re: xwinclip authorisation problem with remote hosts using XDMCP
> This is wrong. 127.0.0.1 is the ip adress for localhost. On every
computer,
> 1
te 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" <[EMAIL PROTECTED]>
To: "Matthew Donald" <[EMAIL PROTECTED]>
Sent: Tuesday, Janu
Hi Harold,
Thanks for your enlightening note. I've placed a 30 second delay in my code
which kludges around the problem. I like your suggestion of retrying
xwinclip every, say 4 seconds, until it connects.
I'm still puzzled by the security issues. Does XDMCP cause the localhost to
lose access
Hi Jean-Marc,
The Telnet Server Admin Tool has a 'Default Shell' setting. Change this to
'C:\cygwin\bin\bash.exe'. This should fix your problem.
BTW, if you don't have the Telnet Server Admin Tool, install the full set of
admin tools off the Win2K Server install CD.
regards Matthew
- Ori
