public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: "Ehud Karni" <ehud@unix.mvs.co.il>
To: cygwin-xfree@cygwin.com
Subject: Re: reset/terminate problems; preventing multiple XWin instances
Date: Thu, 04 Mar 2004 15:11:00 -0000 [thread overview]
Message-ID: <200403041511.i24FBcOQ017243@beta.mvs.co.il> (raw)
In-Reply-To: <404654C2.9010902@tromer.org> (cygwinx2eran@tromer.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 03 Mar 2004 23:57:22 +0200, cygwinx2eran@tromer.org wrote:
>
> On 29-02-2004 14:11, Takuma Murakami wrote:
>
> >> As for preventing multiple instances of XWin
> > This feature is already implemented in my local tree (not
> > port based but mutex based detection).
>
> I see that it's in 4.3.0-50 and working well, but I don't see how the
> current implementation addresses the common task I mentioned:
> "open an xterm; run XWin first if needed"
> If I use a batchfile that always runs XWin and then xterm, from the 2nd
> invocation onwards it will produce the error popup reporting a "Fatal
> error" and directing me a to log file... Not quite what's needed here.[1]
I have a similar problem on Linux (I use VNC virtual DISPLAY).
My solution is to use a shell script and check for the open port by
trying to connect to it. If this fails 5 times, I assume it is not
existing and do whats needed (I do check from remote computers too,
so "whats needed" varies). If the connection succeeds the application
is run with this DISPLAY. I wrote a small program that does the connect
with timeout, and a simple bash script that ensures killing the test
program if it hangs (which sometimes occurs).
Ehud.
- --
Ehud Karni Tel: +972-3-7966-561 /"\
Mivtach - Simon Fax: +972-3-7966-667 \ / ASCII Ribbon Campaign
Insurance agencies (USA) voice mail and X Against HTML Mail
http://www.mvs.co.il FAX: 1-815-5509341 / \
GnuPG: 98EA398D <http://www.keyserver.net/> Better Safe Than Sorry
-----BEGIN PGP SIGNATURE-----
Comment: use http://www.keyserver.net/ to get my key (and others)
iD8DBQFAR0cpLFvTvpjqOY0RAicrAJ9UfYPtmrdkZAEWvN0Wfn0dLT6iTACfW5ih
RTiI7UHJFx241QhRVoJ6V8w=
=Omh6
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-03-04 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 6:41 cygwinx2eran
2004-02-29 13:49 ` Harold L Hunt II
2004-02-29 14:13 ` Eran Tromer
2004-02-29 14:23 ` Harold L Hunt II
2004-02-29 14:23 ` Takuma Murakami
2004-02-29 18:21 ` Harold L Hunt II
2004-03-03 21:54 ` cygwinx2eran
2004-03-04 9:02 ` Takuma Murakami
2004-03-04 15:11 ` Ehud Karni [this message]
2004-03-04 10:37 gkorte
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=200403041511.i24FBcOQ017243@beta.mvs.co.il \
--to=ehud@unix.mvs.co.il \
--cc=cygwin-xfree@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).