Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Mon, 29 Nov 2004 20:25:21 -0500 (EST)
From:	Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To:	cygwin AT cygwin DOT com
To:	David Hinds <dhinds AT sonic DOT net>
cc:	cygwin AT cygwin DOT com
Subject:	Re: A vexing installation problem
In-Reply-To:	<20041130011421.GA20359@sonic.net>
Message-ID:	<Pine.GSO.4.61.0411292016020.14218@slinky.cs.nyu.edu>
References:	<20041129071451 DOT GA15469 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129115158 DOT 046c9120 AT pop DOT prospeed DOT net> <20041129184442 DOT GA30302 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129135305 DOT 046bca10 AT pop DOT prospeed DOT net> <20041129195946 DOT GA4932 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129151309 DOT 046bfba0 AT pop DOT prospeed DOT net> <20041129215220 DOT GA15085 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129171109 DOT 046d1728 AT pop DOT prospeed DOT net> <20041129231740 DOT GA32760 AT sonic DOT net> <6 DOT 2 DOT 0 DOT 14 DOT 0 DOT 20041129181904 DOT 046bf960 AT pop DOT prospeed DOT net> <20041130011421 DOT GA20359 AT sonic DOT net>
MIME-Version:	1.0
X-Scanned-By:	MIMEDefang 2.39

On Mon, 29 Nov 2004, David Hinds wrote:

> On Mon, Nov 29, 2004 at 06:22:35PM -0500, Larry Hall wrote:
> >
> > Yeah, I understand.  This is certainly not your everyday issue, as you've
> > noticed.  I suppose it's worthwhile to look at the settings for the Windows
> > firewall to see if it's being overly restrictive or limiting in some way.
> > Sorry, I don't have any other ideas other than getting down into it with
> > more details...
>
> Ok, this is really odd...
>
> I just noticed that every now and then, when I run a cygwin program
> with the new DLL, it actually does work.  Maybe 10% of the time when I
> invoke a shell, I actually get a working shell, which then appears to
> be fully functional: all its children behave normally.  Also, once I
> have a working shell running, I can also open new shells from the
> desktop and they work 100% of the time.

This suggests some sort of a problem with the Cygwin DLL initialization
code -- something that's very hard to debug.  Try looking at the CVS
history for the Cygwin initialization code between the 1.5.5 and 1.5.6
releases.

As a workaround, you could try adding a Cygwin service that starts
automatically on reboot and would restart indefinitely until it starts up
successfully.  It doesn't have to do anything fancy, a simple 'while true;
do sleep 600; done' should be enough.  If my guess is correct, there's a
10% chance that the service will initialize the Cygwin DLL properly, and
you'll be able to use other Cygwin programs from that point on.

HTH,
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -