Message-ID: <20130311075722.3440@binki>
Date: Mon, 11 Mar 2013 07:57:22 +1000
From: wynfield@gmail.com
To: <cygwin@cygwin.com>
Subject: Re: Setup in infinite tight loop using 100% cpu resource
In-reply-to: Your message of Sun, 10 Mar 2013 16:56:10 +0100	 <87ip4zmep1.fsf@Rainer.invalid>
References: <20130311002225.3704@binki> <87ip4zmep1.fsf@Rainer.invalid>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com


Thanks Achim and Larry for your responses and pointing out that setup.exe should be ran in a ms-windows console.  But, another point I was making,  is that in my opinion, setup.exe should not get into an infinite loop goobling up to 100% cpu usage, that 
setup.exe is out of control and indicates a design or coding flaw.  So when ran with administrators priveledges, unexpected bad side effects might occur.  Ideally, it would detect what ever is wrong and exit gracefully.  If there anyway I help spot the e
rrant code, please let me know and I would try to find a point where it breaks.

Regards

Achim Gratz <Stromeko@nexgo.de> wrote:
> > setup hangs in a tight loop when I try the following command from a cygwin console:
> 
> You should start setup.exe from a cdm window, not a Cygwin console.
> Once you do this, setup.exe does take a few seconds (or up to two
> minutes if the package repository is on a network drive) from the time
> the windows pops up and the packages are listed on the console and the
> window becomes responsive again.
> 
> 
> Regards,
> Achim.
> -- ...

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