Message-ID: <20130311080613.3744@binki>
Date: Mon, 11 Mar 2013 08:06:13 +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


Would using the 'run' command do this so one would not have to start up an instance of a cdm window? 

Example:
$ Run $c/cygwin-packages/setup -q -n -D -K http://cygwin.com/setup.exe.sig  -l C:\cygwin-packages  -R C:\cygwin  -s http://ftp.jaist.ac.jp/pub/cygwin   -P openssh

I'm assuming that setup.exe is expecting DOS style pathnames and RUN does expect posix type pathnames for the command to run.

Thanks  

Achim Gratz <Stromeko@nexgo.de> wrote:
> wynfield@gmail.com writes:
> > 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