X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <4C48A0AE.8060607@cygwin.com> References: <20100722171413.GA943@ns.sdsitehosting.net> <4C48803D.906@cygwin.com> <20100722184328.GA3431@ns.sdsitehosting.net> <4C48A0AE.8060607@cygwin.com> Date: Fri, 23 Jul 2010 13:53:24 +1200 Message-ID: Subject: Re: Cygwin command line takes a long time to start From: David Antliff To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 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 On Fri, Jul 23, 2010 at 07:49, Larry Hall (Cygwin) wrote: > OK then the easiest thing to do is add "set -x" to your ~/.bash_profile > and watch where the delay happens as the statements scroll by. Ah, that's useful - I also have a 10-second-or-so delay when mintty starts. By using a bunch of 'echo' commands and that set -x (which of course extends the time, but at least makes it clear if anything is 'hanging') it's clear to me that the majority of the delay (about 6 seconds) happens before .bash_profile executes. I am loading bash_completion and it does take about 5 seconds, but that's the last thing to run before the prompt appears, and the delay is happening before that. How would one go about debugging the bash or mintty startup before .bash_profile is read? -- David. -- 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