This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
RE: significant delay in xinit detected
- From: "Ralf Habacker" <Ralf dot Habacker at freenet dot de>
- To: "Harold Hunt" <huntharo at msu dot edu>,"Kde-Cygwin" <kde-cygwin at kde dot org>,"Cygwin-Xfree" <cygwin-xfree at sources dot redhat dot com>
- Date: Thu, 6 Jun 2002 00:24:13 +0200
- Subject: RE: significant delay in xinit detected
Hi Harold,
relating to the subject I've found some details:
In xinit.c/startserver() I found the following comment
/*
* kludge to avoid race with TCP, giving server time to
* set his socket options before we try to open it,
* either use the 15 second timeout, or await SIGUSR1.
*
* If your machine is substantially slower than 15 seconds,
* you can easily adjust this value.
*/
alarm (15);
The problem is that if someone uses an .xserverrc file, which starts the xserver
as a sub process, the signal SIGUSR1 never comes to xinit and xinit runs into
the timeout.
A solution for this is
1) avoid a sub shell in .xserverrc :
$cat ~/.xserverrc
exec X <x-related-options>
instead of
$cat ~/.xserverrc
X <x-related-options>
This is described in some older docus like
http://www.stllinux.org/meeting_notes/1997/0619/startx.html
or
2) adding the options in the server part of startx
$ startx -- <x-related-options>
I've taken a look into the cygwin/xfree user guide
http://xfree86.cygwin.com/docs/ug/using.html#using-starting-startx and found
nothing about this topic.
What do you mean, should this not be added to the startx section (at least
solution 1)?
Regards
Ralf
> -----Original Message-----
> From: cygwin-xfree-owner@cygwin.com
> [mailto:cygwin-xfree-owner@cygwin.com]On Behalf Of Ralf Habacker
> Sent: Friday, May 31, 2002 6:14 PM
> To: Kde-Cygwin; Cygwin-Xfree
> Subject: RE: significant delay in xinit detected
>
>
>
> > while working with kde/cygwin and xfree/cygwin I recognized a significant
> > timeout of xinit, after starting the x server and before starting the x
> > client relevant stuff. It seems that xinit goes into a timeout while
> > waiting for
> > the X process, because the delay does not depend on how long the
> xserver needs
> > (I recognized this on a very fast machine, on which the xserver
> only needs 1/2
> > second to start). xinit waits then 5 seconds before starting the .xinitrc
> > script.
>
> Looking a little deeper into the source shows that the timeout is
> about 15 sec,
> not only 5, and it seems that xinit does not recognizes the running x process.
>
> Ralf
>
>