From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31821 invoked by alias); 3 Jul 2014 22:54:15 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Received: (qmail 31726 invoked by uid 89); 3 Jul 2014 22:54:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-HELO: p3plsmtpa06-05.prod.phx3.secureserver.net Received: from p3plsmtpa06-05.prod.phx3.secureserver.net (HELO p3plsmtpa06-05.prod.phx3.secureserver.net) (173.201.192.106) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 03 Jul 2014 22:54:05 +0000 Received: from [10.0.1.110] ([72.209.18.161]) by p3plsmtpa06-05.prod.phx3.secureserver.net with id Myu31o00E3UWwwg01yu4j0; Thu, 03 Jul 2014 15:54:04 -0700 Message-ID: <53B5DF06.5050203@codespunk.com> Date: Thu, 03 Jul 2014 22:54:00 -0000 From: "Matt D." User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com Subject: Re: Automatic X server startup References: <000a01cf79aa$8d1c7f50$a7557df0$%fedin@samsung.com> <5384AD24.4080504@dronecode.org.uk> <004001cf7a74$5c6b3ac0$1541b040$%fedin@samsung.com> <538C82AF.9080702@dronecode.org.uk> In-Reply-To: <538C82AF.9080702@dronecode.org.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-07/txt/msg00001.txt.bz2 I know this thread is a bit old now but I just wanted to mention my solution. I've added X to start in a separate "screen" in my .bash_profile. That way every time I log into Cygwin, X is always available. It's kind of like the previous suggestion of adding it to Windows startup, but I have it more closely coupled to Cygwin. Matt D. On 6/2/2014 9:57 AM, Jon TURNEY wrote: > On 28/05/2014 13:57, Pavel Fedin wrote: >>> I believe this is arranged using launchd on OS X, which listens on the >>> socket the X server will use, and starts the X server when something >>> connects. >>> >>> Unfortunately, there is no similar system facility on Windows. >> >> But it should be possible to make xlib a little bit more smart, >> isn't it ? It could automatically run X server when a connection is >> attempted but refused. So we would achieve the same effect as on MacOS. >> We could e. g. have some directory like /etc/X11/autostart, to be >> examined by xlib. If it detects that e. g. :0 screen is not >> accessible, it would attempt to look up 0.xlaunch file there and run >> "xlaunch -run /etc/X11/autostart/0.xlaunch" command. >> What do you think ? I could implement this idea if you have no time >> to work on that, i believe it should be very easy. > > Patches are always welcome, so please feel free to work on this if you > like. > > I have my doubts that that it's straightforward to add this in libX11 in > a way that is generally useful (for e.g.: there would be a race > condition if two processes both try to start the server at the same > time, there's much room for confusion about how to specify the X server > options to be used, if it could be started explicitly for the start > menu, or implicitly by libX11,...) > >>> You can achieve a somewhat similar effect by copying the X server >>> shortcut to the startup group to start it automatically at login, at >>> the cost of slowing down system startup somewhat. >> >> Heh, it's already slow because of antivirus and other corporate >> stuff (i cannot disable it). Running on demand would be better. > > You might consider looking at starting it from launchd or perhaps xinitd > if possible, and then just that can be started by the X server shortcut, > or at startup. > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/