DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=DHAyCUl9hH8/RiGR
	2WisdS8MvfcMyBnQxy+1t7Pb8CQ/m47QGdk+GUJay+AY7hnK8hsNwYgD2gCwVgNJ
	pQcISGNbBRfgPoQMY3nMtB32zA9tY2WSJAbkj/0eGgUnvZFCcy8xbAQfKnmHI3tC
	sQ3m+hRSw/vUUBJN7/q3Oeo9c2s=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-id: <51FF0CF0.30807@cygwin.com>
Date: Sun, 04 Aug 2013 22:24:48 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: checkX problem or misunderstanding
References: <20130803175444 DOT 3628 AT binki> <51FEFA60 DOT 2050707 AT cygwin DOT com> <20130805105021 DOT 1776 AT binki>
In-reply-to: <20130805105021.1776@binki>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 8/4/2013 9:50 PM, wynfield AT gmail DOT com wrote:
> Larry Hall wrote:
>>> Re: checkX
>>>
>>>     $ checkX --version
>>>       run2 0.4.2
>>>
>>> checkX doesn't work as I understand the description below:
>>>
>>> "DESCRIPTION
>>>          Determines  if  X is installed, Xserver is running on specified DISPLAY
>>>          and will accept clients. Returns 0 if yes, nonzero otherwise"
>>>
>>>
>>> Environment / Procedure to duplicate the error:
>>>
>>>    - I have an X11 server running, started in pty0, where I will test checkX
>>>
>>>    - In this pty0, I start an X11 server, which from the xinitrc starts up another mintty
>>>       terminal, pty1 with Display environment variable set to :0
>>>
>>>    - Testing checkX in pty1 (which has DISPLAY set) returns a 0 or successful result.
>>>      checkX :0  --> returns 0
>>>
>>>    - Moving back to pty0 and running the same command with the same argument gives:
>>>      checkX :0  --> return 1 and error condition or no server available.
>>>
>>>
>>> However, if I simply manually set DISPLAY=:0 in pty0   X11 clients will run.
>>>
>>> -  export DISPLAY=127.0.0.1:0
>>> -  checkX :0  --> Nnw reports an o.k. this server is useable.
>>>
>>> If one relied on checkX the runing server would be missed.  It is doing
>>> nothing that a check if DISPLAY var is set or not andn then possible
>>> testing it.  It should has used the value :0 I sent it and do some X11
>>> stuff I am not aware of.
>>
>> Perhaps we're misunderstanding your confusion here.  Can you explain what
>> about Chuck's description of checkX at the link below isn't clear?
>>
>> <http://cygwin.com/ml/cygwin/2013-08/msg00009.html>
>>
>>
>> --
>> Larry
>
> It is clearly written in my message, in fact in imported it from the
> checkX documentation. What part of the problem I'm describing is not clear
> to you?
>
> "DESCRIPTION
>           Determines  if  X is installed, Xserver is running on specified DISPLAY
>           and will accept clients. Returns 0 if yes, nonzero otherwise""
>
> In fact:
>    checkX :0 returns a false when, but the X11 server on :0 will accept client
> requests.

I guess I'm not clear why you're not using the syntax Chuck recommends in
his message (see the link to it that I included above).  He stated you need
to use the '--display' flag.  Here's a quote from Chuck in that message:

>> You have to tell IT where you think the X server is running, and it
>> willtell you if it can contact a server there. So:
>>
>> $ checkX --display=127.0.0.1:0.0
>> [exits with status value 0 or 1]
>>

So, does that syntax work as Chuck described it?

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple