X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: <20100722171413.GA943@ns.sdsitehosting.net> <4C48803D.906@cygwin.com> <20100722184328.GA3431@ns.sdsitehosting.net> <4C48A0AE.8060607@cygwin.com> Date: Fri, 23 Jul 2010 04:59:47 +0100 Message-ID: Subject: Re: Cygwin command line takes a long time to start From: Andy Koppe To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 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 23 July 2010 02:53, David Antliff 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. Try the same with /etc/profile as well, after first backing it up. Scripts in /etc/profile.d might be involved too. Andy -- 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