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:from:date:to:subject:in-reply-to :references; q=dns; s=default; b=Ek553k3vrT9pX7lNZqEyMRx3PIcyIgl x7RIUVsxdvhKrfkOrUPgFAxoPLo8M96q7JTECUnnU88BDlgLBeYoU2KvzVhsHqnX YRnUeLLBqjCUCC341c0VfCBiTtMvDoXUy0RYsF27F5RuWXZ0uQI8p24NTqo25vWq Lq+Y+fdXW+qo= 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:from:date:to:subject:in-reply-to :references; s=default; bh=pvIxt3u51ctgckyzT/AJO6njIDs=; b=n5quo qU5EjcvGjN5OLLsg4PJrAYKfwg6UtqequgHKlFKSxh4RJH37gmUw4FCT57tTZIU/ +Pd9M/EEggeKagHPcM9Uk8GZZLBZjmpQh+uXUd0oAjRqW7w/bU2XbSCLnAXdyFB5 XCN7qXK5B1TgK29t5wlIRsBsTmgq4gxP4kGrpc= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_NO,RCVD_IN_NIX_SPAM,RDNS_NONE,SPF_NEUTRAL autolearn=no version=3.3.1 Message-ID: <20130805140149.2596@binki> From: "d.henman" Date: Mon, 05 Aug 2013 14:01:49 +0900 To: Subject: Re: checkX problem or misunderstanding In-reply-to: Your message of Sun, 04 Aug 2013 23:11:13 -0400 <51FF17D1.2070303@cwilson.fastmail.fm> References: <20130803175444 DOT 3628 AT binki> <51FEFA60 DOT 2050707 AT cygwin DOT com> <20130805105021 DOT 1776 AT binki> <51FF0CF0 DOT 30807 AT cygwin DOT com> <51FF17D1 DOT 2070303 AT cwilson DOT fastmail DOT fm> Update: checkX does work of course. My problem was: 1. I was setting the DISPLAY environment variable which X11 based clients use and expected checkX to use it as well. 2. I specified the X11 server to try, incorrectly as $ checkX 127.0.0.1:0, without the -d option. For some reason I had it in my head that usage was: checkX [options] . Hower, checkX works when server is specified with the -d option as documented. E.g. $ checkX -d 127.0.0.1:0 THanks for the input to help me find this. My apologies for not spotting this sooner. Regards, Charles Wilson > On 8/4/2013 10:24 PM, Larry Hall (Cygwin) wrote: > > On 8/4/2013 9:50 PM, wynf... wrote: > >> 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: > > To be fair, checkX *should* use the $DISPLAY variable if --display/-d > is not specified on the command line. This appears, from reading the > email thread, to be a real issue. > > However, I won't be able to investigate further for at least a > week...and will have only intermittent internet access until then. > > -- > Chuck > -- 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