public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: wynfield@gmail.com
To: <cygwin@cygwin.com>
Subject: Re: checkX problem or misunderstanding
Date: Mon, 05 Aug 2013 01:50:00 -0000	[thread overview]
Message-ID: <20130805105021.1776@binki> (raw)
In-Reply-To: Your message of Sun, 04 Aug 2013 21:05:36 -0400         <51FEFA60.2050707@cygwin.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

  reply	other threads:[~2013-08-05  1:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-03  8:54 wynfield
2013-08-05  1:06 ` Larry Hall (Cygwin)
2013-08-05  1:50   ` wynfield [this message]
2013-08-05  2:25     ` Larry Hall (Cygwin)
2013-08-05  3:11       ` Charles Wilson
2013-08-05  3:37         ` Christopher Faylor
2013-08-05  8:14           ` Corinna Vinschen
2013-08-06  0:27             ` Christopher Faylor
2013-08-05  5:01         ` d.henman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130805105021.1776@binki \
    --to=wynfield@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).