X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <4899EC23.8030605@nc.rr.com> <489C668C.2070200@nc.rr.com> Subject: RE: Cygwin 1.5.25 : Very slow command Date: Fri, 8 Aug 2008 17:11:32 +0100 Message-ID: <001a01c8f971$6ca9b0e0$9601a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <489C668C.2070200@nc.rr.com> 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 Burt Silverman wrote on 08 August 2008 16:30: > Adding "title" to the CYGWIN variable (e.g., CYGWIN = title) in > Cygwin.bat as per the user manual gives a tremendous psychological > advantage, lowering the slow start pain, as one can see that things are > really happening. "ls" is working perfectly fine -- I will reboot if I > ever see it behave slowly again compared to Windows native "dir" command. Another way to investigate is to edit Cygwin.bat, and add the "-x" option to the line where it starts up bash. That option makes bash print out every command it executes (from scripts, as well as when typed at the keyboard), so you can see even better what's happening at each stage and which goes wrong. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/