Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 From: "Bernard A Badger" To: "Joe Buehler" , Subject: RE: Cygwin is SLOW. Date: Tue, 16 Jul 2002 10:34:46 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <3D342A73.8050802@hekimian.com> X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal > -----Original Message----- > From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf > Of Joe Buehler > Bernard A Badger wrote: > > > So, chmod has to be searched for over my path, and ends up coming over the > > network. No wonder it's slow. > > That's a good point -- the value of PATH can cause poor performance on > UNIX machines. Commands that are most frequently used should be in > directories at the beginning of PATH. > > Joe Buehler Yes, but... Don't let speed override correctness. This is particularly critical for Cygwin users since may override many windows functions. I don't put D:\cygwin\bin in my windows path for that very reason. If I do, I usually add it at the end of the path, even though that's slower. I am primarily a Windows user, and I don't want to mess up my Windows programs and scripts. If I need real Cygwin power, I use the bash shell with a Cygwin-first path. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/