X-Recipient:	archive-cygwin AT delorie DOT com
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:to:subject:in-reply-to
	:references; q=dns; s=default; b=SSyJeLk0+0jNAN3PDXtWklkA7fUzj8V
	KqBcJduZOwL34Sixi36A4vwA5ZvbqnHDq731jfNa7iYs2CeLawkKVehDchAr55TI
	n2T1vxOCJ+EqgQchW9LKDiUMr3Jn2J2lAWvRNTVU0Mt5kN1GJmBBi68LcSpNGtoX
	tb6YpvsMKAv0=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:to:subject:in-reply-to
	:references; s=default; bh=eSf4m012goTbUDlQ+dYN0TuRLps=; b=vAhbp
	5sgl4XTewvOhJGl4doFmLqfcQCk3McNxKHIlPYakVDXRLZMm3qDc0WF9EwWpNdU9
	8KUwkRDuSZM50VWazMILoCMF3xx2xQ8nI0vNcnze6QuOE87eN9SEAbT6O/hbKOHh
	LXXYYM4CwRpG411vcnVxqmW1WCTn1HwkmiiMOE=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status:	No, score=-0.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RDNS_NONE,SPF_NEUTRAL autolearn=no version=3.3.1
Message-ID:	<20130805105021.1776@binki>
Date:	Mon, 05 Aug 2013 10:50:21 +0900
From:	wynfield AT gmail DOT com
To:	<cygwin AT cygwin DOT com>
Subject:	Re: checkX problem or misunderstanding
In-reply-to:	Your message of Sun, 04 Aug 2013 21:05:36 -0400 <51FEFA60.2050707@cygwin.com>
References:	<20130803175444 DOT 3628 AT binki> <51FEFA60 DOT 2050707 AT cygwin DOT com>

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.

Exporting DISPLAY=:0 and running emacs, for example, demonstrates that X11 is available and accepting clients.


> _____________________________________________________________________
end.

--
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

- Raw text -