This is the mail archive of the cygwin-xfree mailing list for the Cygwin XFree86 project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
--On Monday, February 16, 2009 17:40:15 +0100 Franz di Coccio wrote:
Marco,
your suggestion to insert
%CYGWIN_ROOT%\bin\sleep 4
before the xterm launch instruction
%RUN% xterm -e /usr/bin/bash -l
in starxwin.bat did the trick! Thanks a lot! Grazie!
F
PS That's a weird behaviour, anyway... I wonder why the pause is needed only for the first execution after the system boot. Whatever... Now it works :)
The problem seems to be the one that prompted the thread that contains this message:
<http://cygwin.com/ml/cygwin-xfree/2005-04/msg00018.html>
As I understand it, the process that starts the X server finishes before the X server is ready to accept connections. This means that there is then a race condition between the X server start up and the next command in the startup script. If the server is ready first all is well but if not, the next command - xterm - fails to connect and gives up.
The real solution, is to use startx/xinit, as that actually has code to wait until the X server is accepting connections before starting the clients.
-- 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/
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |