Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 29 Nov 2004 20:25:21 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin@cygwin.com To: David Hinds cc: cygwin@cygwin.com Subject: Re: A vexing installation problem In-Reply-To: <20041130011421.GA20359@sonic.net> Message-ID: References: <20041129071451.GA15469@sonic.net> <6.2.0.14.0.20041129115158.046c9120@pop.prospeed.net> <20041129184442.GA30302@sonic.net> <6.2.0.14.0.20041129135305.046bca10@pop.prospeed.net> <20041129195946.GA4932@sonic.net> <6.2.0.14.0.20041129151309.046bfba0@pop.prospeed.net> <20041129215220.GA15085@sonic.net> <6.2.0.14.0.20041129171109.046d1728@pop.prospeed.net> <20041129231740.GA32760@sonic.net> <6.2.0.14.0.20041129181904.046bf960@pop.prospeed.net> <20041130011421.GA20359@sonic.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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@cs.nyu.edu ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.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/