X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: cygwin@cygwin.com Subject: Re: 1.7.[67]: getting bash prompt takes > 50 seconds References: <4C7F0C3E.5020904@hicorp.co.jp> Date: Thu, 02 Sep 2010 09:25:56 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Matthias Andree" Message-ID: In-Reply-To: <4C7F0C3E.5020904@hicorp.co.jp> User-Agent: Opera Mail/10.61 (Linux) X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Am 02.09.2010, 04:30 Uhr, schrieb Mark Callow: > > > Hi Andrey, > >> Did you tried to *uninstall* bash-completion? > I have now. Surprisingly (to me) it worked. The time-to-prompt has > dropped to ~5 seconds on one of the machines and ~8 seconds on the > other. Both are still too long but a vast improvement over 50 seconds. You can open a cmd.exe terminal window and type "bash --login -x" (or -xv) to figure if it spends a particularly long time in a certain area of the .bashrc execution, however, Cygwin is indeed a lot slower than Unix when shell scripting, because creating Unix processes is very costly in Cygwin, and that is an operation that happens a lot in shell scripts... -- Matthias Andree -- 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