X-Spam-Check-By: sourceware.org Message-Id: <1139243098.31153.253660398@webmail.messagingengine.com> From: "Brett Serkez" To: cygwin AT cygwin DOT com Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="ISO-8859-1" MIME-Version: 1.0 References: <020620061512 DOT 1594 DOT 43E767490006AAD30000063A22007507840A050E040D0C079D0A AT comcast DOT net> Subject: Re: default PATH In-Reply-To: <020620061512.1594.43E767490006AAD30000063A22007507840A050E040D0C079D0A@comcast.net> Date: Mon, 06 Feb 2006 11:24:58 -0500 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > Try opening a cmd.com window in c:\cygwin\bin (or whatever it is > named), then running 'bash --login -xv' to see every command executed > by bash during startup. Maybe that will help you pinpoint the > culprit. This really helps understand why it takes so long to open a bash shell, the login scripts have allot of work to do. I've noticed that login time has gotten much better with the latest cygwin dll, looks like id, hostname and sed processing slow down the login process. Brett ---------------------------------------------------------------- Brett C. Serkez, Techie -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/