public inbox for
help / color / mirror / Atom feed
From: Jim Garrison <>
Subject: Launching Cygwin/X in background with no clients
Date: Tue, 03 Feb 2015 05:12:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2/2/2015 5:21 PM, Yaakov Selkowitz wrote:
> On Mon, 2015-02-02 at 16:52 -0800, Jim Garrison wrote:
>> I updated Cygwin (which pulled in a bunch of Cygwin-X updates) and
>> now startxwin no longer works.  According to the log (below) it starts
>> the XServer successfully but then shuts down.
>> My .startxwinrc is an empty (zero-length) file to prevent automatic
>> launching of the default clients, which I don't need.


I want to start an X server in the background, with no visible
clients, if it's not already running, whenever I launch a mintty
session. X should continue to run even if the mintty session that
started it is closed.

Currently I have the following in my .bash_profile

   ps -ef|grep -q XWin || nohup setsid startxwin 2>startxwin.log&

This now works again after adding "exec sleep infinity" in
.startxwinrc, but I can't help feel my whole approach is a bad hack.
Both nohup and setsid seem to be required. Without setsid the mintty
will hang if I attempt to close it with exit or ^D, and without nohup
the X server terminates whenever the first mintty session is closed.

Is there a cleaner way to accomplish this objective?

Jim Garrison

Unsubscribe info:
Problem reports:

  reply	other threads:[~2015-02-03  5:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03  0:53 startxwin failing after most recent updates Jim Garrison
2015-02-03  1:21 ` Yaakov Selkowitz
2015-02-03  5:12   ` Jim Garrison [this message]
2015-02-03 14:13     ` Launching Cygwin/X in background with no clients Mark Hansen

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:

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

  git send-email \ \ \ \

* 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).